Enable configuration of startupProbe in containers created using Helm (…

…minio#1370)
allanrogerr · Dec 15, 2022 · 15a8eb4 · 15a8eb4
1 parent 0689133
commit 15a8eb4
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/helm/tenant/templates/tenant.yaml b/helm/tenant/templates/tenant.yaml
@@ -120,6 +120,10 @@ spec:
   liveness:
     {{- toYaml . | nindent 4 }}
   {{- end }}
+  {{- with (dig "startup" (dict) .) }}
+  startup:
+    {{- toYaml . | nindent 4 }}
+  {{- end }}
   {{- with (dig "exposeServices" (dict) .) }}
   exposeServices:
     {{- toYaml . | nindent 4 }}

diff --git a/helm/tenant/values.yaml b/helm/tenant/values.yaml
@@ -105,6 +105,9 @@ tenant:
   # Readiness Probe for container readiness. Container will be removed from service endpoints if the probe fails.
   # Refer https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
   readiness: { }
+  # Startup Probe for container startup. Container will be restarted if the probe fails.
+  # Refer https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
+  startup: { }
   ## exposeServices defines the exposure of the MinIO object storage and Console services.
   ## service is exposed as a loadbalancer in k8s service.
   exposeServices: { }