-
Notifications
You must be signed in to change notification settings - Fork 689
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
Nodes resource mismatch #1234
Comments
/kind support @19bcs2405 Per README:
As the description suggests, these strategies do not consider actual utilization but rather resource allocation (poor naming). There are a few open PRs that look at utilization such as: Given that they behave correctly, I am going to close this issue but feel free to reopen if you think there is a bug. |
/remove-kind bug |
@a7i Is there any way to descheduler get exact Resources like kubectl top node. |
I have install descheduler on my cluster. kubectl top node command gives different output than descheduler.
Descheduler shows All nodes are underutilized. but when used kubectl top node command, its show many off nodes are on 100% utilization.
How to fix this bug. Please guide me.
The text was updated successfully, but these errors were encountered: