-
Notifications
You must be signed in to change notification settings - Fork 668
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
Cluster Size check shouldn't exit process when running as Deployment #1298
Comments
I have similar case, tbh I wanted to limit descheduler scope to just nodes with certain label, but with this behaviour this is not possible. I am planning to use descheduler with I have work aoruneded that by adding node selector in policy directly, however this is suboptimal - I have over 1000 nodes in my cluster and I actually want descheduler to watch just few of them |
I also found #469 however not sure what was fixed in that issue |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". 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. |
I would say that this is more of a bug, as this affects all single node kubernetes clusters (minikube, docker desktop) |
Is your feature request related to a problem? Please describe.
When there are 0 or 1 nodes the descheduler loop returns error
the cluster size is 0 or 1
& the process exits.This doesn't play nicely when the descheduler is running as a Deployment - the pod goes into
CrashLoopBackOff
due to the repeated early exits.Describe the solution you'd like
When the descheduler is running as a Deployment
the cluster size is 0 or 1
check shouldn't exit the process. The process should remain running until the next iteration.Something like (in
runDeschedulerLoop
):Describe alternatives you've considered
What version of descheduler are you using?
descheduler version:
0.28.0
Additional context
Example logs
The text was updated successfully, but these errors were encountered: