-
Notifications
You must be signed in to change notification settings - Fork 650
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
Question about on how pods are evicted #122
Comments
Not in current implementation. Could you describe your use case why would you want to have that? In general, descheduler's aim to rebalance overall cluster, sometimes a set of nodes in a cluster. The thing you are looking for seems like just eviction of pods in namespaces with specific labels. So its possible, but we would have to make sure its use case does not conflict with the real goals of descheduler. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi, I would like to know if it possible to define deschedule policies only for namespaces with a specific label, any idea ?
Thanks.
The text was updated successfully, but these errors were encountered: