Skip to content
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

Closed
slawekww opened this issue Aug 18, 2023 · 5 comments · Fixed by #519
Closed

Cannot define liveness/readiness probes via helm chart #508

slawekww opened this issue Aug 18, 2023 · 5 comments · Fixed by #519
Labels
bug Something isn't working

Comments

@slawekww
Copy link

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:

Steps to Reproduce the Problem

  1. use helm chart for keda

Specifications

  • KEDA Version: chart version 2.11.2
  • Platform & Version: N/A
  • Kubernetes Version: N/A
  • Scaler(s): N/A
@slawekww slawekww added the bug Something isn't working label Aug 18, 2023
@JorTurFer
Copy link
Member

Are you willing to adding support for it?

@slawekww
Copy link
Author

If it is not urgent, I may try to implement as it is defined in bitnami template:
https://github.com/bitnami/charts/blob/main/template/CHART_NAME/values.yaml

I may have time within the month as it is not urgent.

@JorTurFer
Copy link
Member

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)

@dttung2905
Copy link
Contributor

Hi @slawekww , I'm working on a PR. May I know exactly which value you want to parameterise ?

@slawekww
Copy link
Author

HI @dttung2905, I plan to add values in values.yaml:

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 timeoutSeconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants