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

Targeted Pod Removal During Scaling Down #6124

Closed
milad2golnia opened this issue Sep 1, 2024 · 6 comments
Closed

Targeted Pod Removal During Scaling Down #6124

milad2golnia opened this issue Sep 1, 2024 · 6 comments
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity

Comments

@milad2golnia
Copy link

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

@milad2golnia milad2golnia added feature-request All issues for new features that have not been committed to needs-discussion labels Sep 1, 2024
@milad2golnia milad2golnia changed the title Scale down deterministically Targeted Pod Removal During Scaling Down Sep 1, 2024
@JorTurFer
Copy link
Member

Hello,
Sadly KEDA doesn't provide any option to handle this as we rely on the HPA controller and it's the HPA controller the responsible of handling the scaling on k8s side

@milad2golnia
Copy link
Author

@JorTurFer
Thank you for your response. It was very helpful. You can close the issue if you believe it's outside the scope of KEDA. However, I suggest adding a note in the documentation, as others seem to have encountered the same question, as I mentioned in my issue.

@JorTurFer
Copy link
Member

However, I suggest adding a note in the documentation, as others seem to have encountered the same question, as I mentioned in my issue.

This can be nice! Are you willing to open a PR to docs repo? https://github.com/kedacore/keda-docs

@milad2golnia
Copy link
Author

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.

Copy link

stale bot commented Nov 7, 2024

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Nov 7, 2024
Copy link

stale bot commented Nov 17, 2024

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Nov 17, 2024
@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity
Projects
Status: Ready To Ship
Development

No branches or pull requests

2 participants