1 個回答
- 最新
- 最多得票
- 最多評論
0
You might want to try using https://karpenter.sh/ for autoscaling and see if it improves your utilization. It can also consolidate pods to less nodes, but that might not always be appropriate for running jobs
已回答 1 年前
相關內容
AWS 官方已更新 1 年前- AWS 官方已更新 4 個月前
- AWS 官方已更新 3 個月前
- AWS 官方已更新 2 年前
We are already using Karpenter and it does not solve the problem but instead makes it worse. Karpenter creates much bigger nodes during scale-up, than cluster autoscaler, which are much more underutilized after the load goes away.
To fix the problem we need to be able to adapt the scheduling policy of the kubernetes scheduler to use its bin packing capability. Then new pods would not be spread across all nearly empty nodes but be bin packed on just some nodes which result in some empty nodes which can then be removed by karpenter.