Open slawekww opened 1 year ago
All modern helm chart allows to define custom readiness and liveness probes. In some k8s deployments, timeout of 1s for not enough.
v3.11.1
v1.24.6
2.5.0
Readiness/liveness is fixed and cannot be changed by helm chart:
Liveness: http-get http://:healthz/healthz delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
Add readiness/liveness probes globally for all components or for each components as values.yaml to allow update them by user of helm chart.
Deploy helm chart with flux.
n/a
No response
Describe the bug a clear and concise description of what the bug is.
All modern helm chart allows to define custom readiness and liveness probes. In some k8s deployments, timeout of 1s for not enough.
What's your helm version?
v3.11.1
What's your kubectl version?
v1.24.6
What's the chart version?
2.5.0
What happened?
Readiness/liveness is fixed and cannot be changed by helm chart:
What you expected to happen?
Add readiness/liveness probes globally for all components or for each components as values.yaml to allow update them by user of helm chart.
How to reproduce it?
Deploy helm chart with flux.
Enter the changed values of values.yaml?
n/a
Enter the command that you execute and failing/misfunctioning.
n/a
Anything else we need to know?
No response