-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Targeted Pod Removal During Scaling Down #6124
Comments
Hello, |
@JorTurFer |
This can be nice! Are you willing to open a PR to docs repo? https://github.com/kedacore/keda-docs |
Thank you! I'd love to contribute when I have the time. I'll keep the PR to the docs repo in mind and will try to open one as soon as my schedule allows. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Proposal
I’m looking for a way to determine which pod to remove when scaling down. Assume we have three pods: A, B, and C. I want to scale down by specifically removing pod B. Does KEDA provide an option for this?
Use-Case
This is highly useful in many scenarios. I think the pod-deletion-cost issue is related to this feature, and with it, we could handle pod-deletion-cost programmatically. It also seems that the Scaling down logic discussion is requesting this feature, but the author forgot to submit a feature request.
In general, this is useful when we want to remove idle pods rather than a random pod.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
The text was updated successfully, but these errors were encountered: