Add support for startupProbe in helm chart

Author: ns-bsena

helm/nessie/templates/deployment.yaml

@@ -132,6 +132,16 @@ spec:
             {{- tpl (toYaml .Values.extraEnv) . | nindent 12 }}
             {{- end }}
           {{- include "nessie.containerPorts" . | trim | nindent 10 }}
+          startupProbe:
+            httpGet:
+              path: /q/health/started
+              port: {{ .Values.managementService.portName }}
+              scheme: HTTP
+            initialDelaySeconds: {{ .Values.startupProbe.initialDelaySeconds }}
+            periodSeconds: {{ .Values.startupProbe.periodSeconds }}
+            successThreshold: {{ .Values.startupProbe.successThreshold }}
+            failureThreshold: {{ .Values.startupProbe.failureThreshold }}
+            timeoutSeconds: {{ .Values.startupProbe.timeoutSeconds }}
           livenessProbe:
             httpGet:
               path: /q/health/live

helm/nessie/values.yaml

@@ -1053,6 +1053,19 @@ affinity: {}
 #                values:
 #                  - nessie
 
+# -- Configures the startup probe for nessie pods.
+startupProbe:
+  # -- Number of seconds after the container has started before startup probes are initiated. Minimum value is 0.
+  initialDelaySeconds: 0
+  # -- How often (in seconds) to perform the probe. Minimum value is 1.
+  periodSeconds: 10
+  # -- Minimum consecutive successes for the probe to be considered successful after having failed. Minimum value is 1.
+  successThreshold: 1
+  # -- Minimum consecutive failures for the probe to be considered failed after having succeeded. Minimum value is 1.
+  failureThreshold: 5
+  # -- Number of seconds after which the probe times out. Minimum value is 1.
+  timeoutSeconds: 10
+
 # -- Configures the liveness probe for nessie pods.
 livenessProbe:
   # -- Number of seconds after the container has started before liveness probes are initiated. Minimum value is 0.