-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Kubernetes Workload Scaler: ignore terminated pods #2384
Kubernetes Workload Scaler: ignore terminated pods #2384
Conversation
Signed-off-by: Staffan Olsson <staffan@repos.se>
Signed-off-by: Staffan Olsson <staffan@repos.se>
Signed-off-by: Staffan Olsson <staffan@repos.se>
Signed-off-by: Staffan Olsson <staffan@repos.se>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks for your contribution :)
/run-e2e kubernetes-workload.test* |
Signed-off-by: Staffan Olsson <staffan@repos.se>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks for your contribution ❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @solsson
The kubernetes-workload scaler is great, but I was surprised to discover that it counts terminated pods. While it's useful to have Shutdown or Completed pods stay around to aid for example troubleshooting I fail to come up with a use case where scaling should count them together with running. This PR excludes the two obvious terminated states from the metric value.
Checklist