We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
文章链接:https://blog.tianfeiyu.com/2022/06/30/kubernetes_descheduler/
您提到LowNodeUtilization 和 HighNodeUtilization是按照request 比率进行分配的,这确实不符合实际生产想要的效果 但可以根据实际的场景进行扩展,将其改为基于节点真实的资源使用率,方便讲解下具体思路吗?
The text was updated successfully, but these errors were encountered:
方法挺多的: (1)可以通过公司内部监控配置报警主动触发二次调度; (2)可以在 descheduler 代码中主动从公司内部监控系统获取节点的实际利用率; 我们目前就用的这两个方式。
Sorry, something went wrong.
感谢答复,您指到修改descheduler源码,改为获取实际利用率,是否类似这个pr:kubernetes-sigs/descheduler#1092
或者方便说下您这边代码修改的思路吗?
No branches or pull requests
文章链接:https://blog.tianfeiyu.com/2022/06/30/kubernetes_descheduler/
您提到LowNodeUtilization 和 HighNodeUtilization是按照request 比率进行分配的,这确实不符合实际生产想要的效果
但可以根据实际的场景进行扩展,将其改为基于节点真实的资源使用率,方便讲解下具体思路吗?
The text was updated successfully, but these errors were encountered: