-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot define liveness/readiness probes via helm chart #508
Comments
Are you willing to adding support for it? |
If it is not urgent, I may try to implement as it is defined in bitnami template: I may have time within the month as it is not urgent. |
It's not urgent at all. We plan to cut a release at the end of the month, but helm chart can be released also before or after as it has it's own release cycle (basically, on demand xD) |
Hi @slawekww , I'm working on a PR. May I know exactly which value you want to parameterise ? |
HI @dttung2905, I plan to add values in operator:
# Liveness probes
livenessProbe:
initialDelaySeconds: 25
periodSeconds: 10
timeoutSeconds: 1
failureThreshold: 3
successThreshold: 1
# Readiness probes
readinessProbe:
initialDelaySeconds: 20
periodSeconds: 3
timeoutSeconds: 1
failureThreshold: 3
successThreshold: 1 and use them in charts/keda/templates/manager/deployment.yaml The default would be like it is now and it allows to define values by users, especially |
Expected Behavior
It should be possible to define liveness/readiness probe values, now all is hardcoded and for some systems timeout=1s is not acceptable.
Allow to define those probes at values.yaml for helm chart (at least for manager component).
Actual Behavior
Cannot change those values via current chart:
charts/keda/templates/manager/deployment.yaml
Line 94 in 9fbc236
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: