-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvalues.yaml.j2
177 lines (158 loc) · 6.54 KB
/
values.yaml.j2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
---
global:
postgresqlSecretName: ""
dagsterHome: ""
serviceAccountName: "user-locations"
celeryConfigSecretName: ""
dagsterHome: "/opt/dagster/dagster_home"
postgresqlSecretName: "dagster-postgresql-secret2"
celeryConfigSecretName: "dagster-celery-config-secret"
####################################################################################################
# User Code Deployments: Configuration for user code containers to be loaded via GRPC server. For
# each item in the "deployments" list, a K8s Deployment and K8s Service will be created to run the
# GRPC server that Dagster communicates with to get repository information and the current
# image information. These deployments can be updated independently of the webserver, and Dagster
# will pull the current image for all execution. When using a distributed executor (such as
# Celery-K8s) for pipeline run, the current image will be queried once and used for all
# solid executions for that pipeline run. In order to guarantee that all solid executions within a
# pipeline execution use the same image, we recommend using a unique tag (ie not "latest").
#
# All user code will be invoked within the images.
####################################################################################################
deployments:
- name: "luchtmeetnet-ingestion"
image:
# When a tag is not supplied, it will default as the Helm chart version.
repository: "europe-west4-docker.pkg.dev/{{ project_name }}/dags-areg-euw4-{{ project_short_name }}-prd/luchtmeetnet_ingestion"
tag: {{ version|default("latest", true) }}
# Change with caution! If you're using a fixed tag for pipeline run images, changing the
# image pull policy to anything other than "Always" will use a cached/stale image, which is
# almost certainly not what you want.
pullPolicy: Always
# Arguments to `dagster api grpc`.
# Ex: "dagster api grpc -m dagster_test.test_project.test_jobs.repo -a define_demo_execution_repo"
# would translate to:
# dagsterApiGrpcArgs:
# - "-m"
# - "dagster_test.test_project.test_jobs.repo"
# - "-a"
# - "define_demo_execution_repo"
# The `dagsterApiGrpcArgs` key can also be replaced with `codeServerArgs` to use a new
# experimental `dagster code-server start` command instead of `dagster api grpc`, which takes
# identical arguments but can reload its definitions from within the Dagster UI without
# needing to restart the user code deployment pod.
dagsterApiGrpcArgs:
- "--module-name"
- "luchtmeetnet_ingestion"
- "--host"
- "0.0.0.0"
port: 4265
# Whether or not to include configuration specified for this user code deployment in the pods
# launched for runs from that deployment
includeConfigInLaunchedRuns:
enabled: true
# Additional volumes that should be included in the Deployment's Pod. See:
# https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#volume-v1-core
#
# Example:
#
# volumes:
# - name: my-volume
# configMap: my-config-map
volumes: []
# Additional volume mounts that should be included in the container in the deployment's pod. See:
# See: https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#volumemount-v1-core
#
# Example:
#
# volumeMounts:
# - name: test-volume
# mountPath: /opt/dagster/test_folder
# subPath: test_file.yaml
volumeMounts: []
# Additional environment variables to set.
# These will be directly applied to the daemon container. See
# https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/
#
# Example:
#
# env:
# - name: ENV_ONE
# value: "one"
# - name: ENV_TWO
# value: "two"
env:
- name: ENVIRONMENT
value: "prd"
- name: GCP_PROJECT
value: "jasper-ginn-dagster"
# Additional environment variables can be retrieved and set from ConfigMaps. See:
# https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables
#
# Example:
#
# envConfigMaps:
# - name: config-map
envConfigMaps: []
# Additional environment variables can be retrieved and set from Secrets. See:
# https://kubernetes.io/docs/concepts/configuration/secret/#use-case-as-container-environment-variables
#
# Example:
#
# envSecrets:
# - name: secret
envSecrets:
- name: gcs-access-key-id
- name: gcs-secret-access-key
- name: dagster-secret-redis-host
- name: dagster-secret-redis-username
- name: dagster-secret-redis-password
annotations: {}
nodeSelector: {}
affinity: {}
tolerations: []
podSecurityContext: {}
securityContext: {}
resources:
limits:
cpu: 350m
memory: 500Mi
requests:
cpu: 350m
memory: 500Mi
labels: {}
# Override the default K8s scheduler
# schedulerName: ~
# Readiness probe detects when the pod is ready to serve requests.
# https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes
readinessProbe:
# Readiness probes are enabled by default.
enabled: true
# If `readinessProbe` has no `exec` field, then the following default will be used:
# exec:
periodSeconds: 20
timeoutSeconds: 10
successThreshold: 1
failureThreshold: 3
# As of 0.14.0, liveness probes are disabled by default. If you want to enable them, it's recommended to also
# enable startup probes.
livenessProbe: {}
startupProbe:
enabled: false
service:
annotations: {}
# Specify secrets to run containers based on images in private registries. See:
# https://kubernetes.io/docs/concepts/containers/images/#referring-to-an-imagepullsecrets-on-a-pod
imagePullSecrets: []
serviceAccount:
create: false
# Specifies the name for the service account to reference in the chart. Note that setting
# the global service account name will override this field.
name: ""
annotations: {}
# Whether to bind a role to the service account that allows it to create Kubernetes jobs
rbacEnabled: true
####################################################################################################
# Extra Manifests: (Optional) Create additional k8s resources within this chart
####################################################################################################
extraManifests: []