Closed jmesnil closed 3 years ago
This feature would follow up what we did for readiness and liveness probes:
deploy.startupProbe
is defined (similar to https://github.com/wildfly/wildfly-charts/blob/98e86bb0dd24d7c75131df6d764b9644eeb1a4b5/charts/wildfly-common/templates/_deployment.yaml#L61-L64)readinessProbe
) with maybe a higher failureThreshold: 18
so that the app has 3 minutes (18 * 10 = 180s) to startup.deploy.readinessProbe
)This is superseded by https://github.com/wildfly/wildfly-charts/issues/37
Is your feature request related to a problem? Please describe.
Kubernetes define a specific startup probe for applications that are slow to start: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes
We should provide a way to define such a probe from the Helm Chart.
This would add a
deploy.startupProbe
whose content will be a YAML configuration of the startup probe as defined in https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes