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://leason.top/kubernetes%E8%B4%9F%E8%BD%BD%E6%84%9F%E7%9F%A5%E8%B0%83%E5%BA%A6.html#more
背景kubernetes 的原生调度器只能通过资源请求来调度 pod,这很容易造成一系列负载不均的问题,并且很多情况下业务方都是超额申请资源,因此在原生调度器时代我们针对业务的特性以及评估等级来设置 Requests/Limit 比例来提升资源利用效率。在这种场景下依然存在很多问题: 节点负载不均:原生 Kubernetes Scheduler 根据 Requests 和节点可分配总量
The text was updated successfully, but these errors were encountered:
问题一,有没有啥落地方案可以分析下
Sorry, something went wrong.
@jgfowpa444 问题一,有没有啥落地方案可以分析下
有,后面会专门写一篇文章,说下我们的方案
No branches or pull requests
https://leason.top/kubernetes%E8%B4%9F%E8%BD%BD%E6%84%9F%E7%9F%A5%E8%B0%83%E5%BA%A6.html#more
背景kubernetes 的原生调度器只能通过资源请求来调度 pod,这很容易造成一系列负载不均的问题,并且很多情况下业务方都是超额申请资源,因此在原生调度器时代我们针对业务的特性以及评估等级来设置 Requests/Limit 比例来提升资源利用效率。在这种场景下依然存在很多问题: 节点负载不均:原生 Kubernetes Scheduler 根据 Requests 和节点可分配总量
The text was updated successfully, but these errors were encountered: