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

Chart: Align HPA & KEDA conditions. #10814

Closed
Gacko opened this issue Dec 30, 2023 · 6 comments · Fixed by #11110
Closed

Chart: Align HPA & KEDA conditions. #10814

Gacko opened this issue Dec 30, 2023 · 6 comments · Fixed by #11110
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Gacko
Copy link
Member

Gacko commented Dec 30, 2023

Currently some of the Helm chart templates contain conditions checking if HPA (controller.autoscaling) and/or KEDA (controller.keda) is enabled or not.

The PDB for example only gets rendered if HPA is disabled and the static replica count is greater than 1 or if HPA is enabled and its minimum replica count is greater than 1. KEDA is not being considered here.

The HPA only gets rendered if it's enabled and KEDA is disabled. For KEDA we are only checking if KEDA is enabled, not if HPA is disabled.

There are more examples, so to sum things up: Search for usages of either controller.autoscaling.enabled or controller.keda.enabled and check that both of them are checked in a way it makes sense and is consistent all over the chart.

@Gacko Gacko added the kind/bug Categorizes issue or PR as related to a bug. label Dec 30, 2023
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Dec 30, 2023
@Gacko
Copy link
Member Author

Gacko commented Dec 30, 2023

/assign

@Gacko
Copy link
Member Author

Gacko commented Dec 30, 2023

/priority backlog
/triage accepted

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 30, 2023
Copy link

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 30, 2024
@Gacko
Copy link
Member Author

Gacko commented Jan 30, 2024

/remove-lifecycle frozen

@k8s-ci-robot k8s-ci-robot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 30, 2024
@StuxxNet
Copy link
Contributor

@Gacko if you want I can also give a try on this one based on the last contribution. What do you think? I might need some guidance, but would happily help!

@Gacko
Copy link
Member Author

Gacko commented Mar 11, 2024

I already have something prepared for that locally. Once I pushed it and created a PR for it, I'd be glad to get some review from you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

3 participants