You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: helm/blueapi/README.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,12 @@ A Helm chart deploying a worker pod that runs Bluesky plans
32
32
| podAnnotations | object |`{}`||
33
33
| podLabels | object |`{}`||
34
34
| podSecurityContext | object |`{}`||
35
-
|pvcautodeletion.enabled | bool |`true`||
35
+
|pvcAutoDeletion.enabled | bool |`true`||
36
36
| readinessProbe | object |`{"failureThreshold":2,"httpGet":{"path":"/healthz","port":"http"},"periodSeconds":10}`| Readiness probe, if configured kubernetes will not route traffic to this pod if failed consecutively. This could allow the service time to recover if it is being overwhelmed by traffic, but without the to ability to load balance or scale up/outwards, upstream services will need to know to back off. This is automatically disabled when in debug mode. |
37
-
| resources | object |`{"limits":{"cpu":"2000m","memory":"4000Mi"},"requests":{"cpu":"200m","memory":"400Mi"}}`| Sets the compute resources available to the pod. These defaults are appropriate when using debug mode or an internal PVC and therefore running VS Code server in the pod. In the Diamond cluster, requests must be >= 0.1*limits When not using either of the above, the limits may be lowered. When idle but connected, blueapi consumes ~400MB of memory and 1% cpu and may struggle when allocated less. |
37
+
| resources.limits.cpu | string |`"2000m"`||
38
+
| resources.limits.memory | string |`"4000Mi"`||
39
+
| resources.requests.cpu | string |`"200m"`||
40
+
| resources.requests.memory | string |`"400Mi"`||
38
41
| restartOnConfigChange | bool |`true`| If enabled the blueapi pod will restart on changes to `worker`|
39
42
| securityContext.runAsNonRoot | bool |`true`||
40
43
| securityContext.runAsUser | int |`1000`||
@@ -53,6 +56,5 @@ A Helm chart deploying a worker pod that runs Bluesky plans
53
56
| worker | object |`{"api":{"url":"http://0.0.0.0:8000/"},"env":{"sources":[{"kind":"planFunctions","module":"dodal.plans"},{"kind":"planFunctions","module":"dodal.plan_stubs.wrapped"}]},"logging":{"graylog":{"enabled":false,"url":"tcp://graylog-log-target.diamond.ac.uk:12231/"},"level":"INFO"},"scratch":{"repositories":[],"root":"/workspace"},"stomp":{"auth":{"password":"guest","username":"guest"},"enabled":false,"url":"tcp://rabbitmq:61613/"}}`| Config for the worker goes here, will be mounted into a config file |
54
57
| worker.api.url | string |`"http://0.0.0.0:8000/"`| 0.0.0.0 required to allow non-loopback traffic If using hostNetwork, the port must be free on the host |
55
58
| worker.env.sources | list |`[{"kind":"planFunctions","module":"dodal.plans"},{"kind":"planFunctions","module":"dodal.plan_stubs.wrapped"}]`| modules (must be installed in the venv) to fetch devices/plans from |
56
-
| worker.logging | object |`{"graylog":{"enabled":false,"url":"tcp://graylog-log-target.diamond.ac.uk:12231/"},"level":"INFO"}`| Configures logging. Port 12231 is the `dodal` input on graylog which will be renamed `blueapi`|
57
59
| worker.scratch | object |`{"repositories":[],"root":"/workspace"}`| If initContainer is enabled the default branch of python projects in this section are installed into the venv *without their dependencies*|
58
60
| worker.stomp | object |`{"auth":{"password":"guest","username":"guest"},"enabled":false,"url":"tcp://rabbitmq:61613/"}`| Message bus configuration for returning status to GDA/forwarding documents downstream Password may be in the form ${ENV_VAR} to be fetched from an environment variable e.g. mounted from a SealedSecret |
Copy file name to clipboardExpand all lines: helm/blueapi/values.schema.json
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -174,7 +174,7 @@
174
174
"podSecurityContext": {
175
175
"type": "object"
176
176
},
177
-
"pvcautodeletion": {
177
+
"pvcAutoDeletion": {
178
178
"type": "object",
179
179
"properties": {
180
180
"enabled": {
@@ -206,7 +206,6 @@
206
206
}
207
207
},
208
208
"resources": {
209
-
"description": "Sets the compute resources available to the pod. These defaults are appropriate when using debug mode or an internal PVC and therefore running VS Code server in the pod. In the Diamond cluster, requests must be \u003e= 0.1*limits When not using either of the above, the limits may be lowered. When idle but connected, blueapi consumes ~400MB of memory and 1% cpu and may struggle when allocated less.",
210
209
"type": "object",
211
210
"properties": {
212
211
"limits": {
@@ -405,7 +404,6 @@
405
404
}
406
405
},
407
406
"logging": {
408
-
"description": "Configures logging. Port 12231 is the `dodal` input on graylog which will be renamed `blueapi`",
# This is for setting up a service more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/
50
+
# This is for setting up a service more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/
52
51
service:
53
52
# This sets the service type more information can be found here: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
54
53
# -- To make blueapi available on an IP outside of the cluster prior to an Ingress being created, change this to LoadBalancer
@@ -76,13 +75,13 @@ ingress:
76
75
# hosts:
77
76
# - chart-example.local
78
77
79
-
# -- Sets the compute resources available to the pod.
80
-
# These defaults are appropriate when using debug mode or an internal PVC and therefore
81
-
# running VS Code server in the pod.
82
-
# In the Diamond cluster, requests must be >= 0.1*limits
83
-
# When not using either of the above, the limits may be lowered.
84
-
# When idle but connected, blueapi consumes ~400MB of memory and 1% cpu
85
-
# and may struggle when allocated less.
78
+
# -- Sets the compute resources available to the pod.
79
+
# These defaults are appropriate when using debug mode or an internal PVC and therefore
80
+
# running VS Code server in the pod.
81
+
# In the Diamond cluster, requests must be >= 0.1*limits
82
+
# When not using either of the above, the limits may be lowered.
83
+
# When idle but connected, blueapi consumes ~400MB of memory and 1% cpu
84
+
# and may struggle when allocated less.
86
85
resources:
87
86
# We usually recommend not to specify default resources and to leave this as a conscious
88
87
# choice for the user. This also increases chances charts run on environments with little
0 commit comments