I followed the relevant documentation to test Resource overcommitment , there seems to be a problem

[googs1025]

refer to: https://gokatalyst.io/docs/user-guide/resource-overcommitment/ 我使用这个文档去测试超分比的示例，看着好像没生效？

root@VM-0-12-ubuntu:/home/ubuntu# kubectl get pod -o wide |grep busybox-deployment-overcommit |awk '{print $3}' |sort |uniq -c
     19 Pending
      1 Running
root@VM-0-12-ubuntu:/home/ubuntu# kubectl get pod -o wide |grep busybox-deployment-overcommit |awk '{print $3}' |sort |uniq -c
     19 Pending
      1 Running
root@VM-0-12-ubuntu:/home/ubuntu# kubectl get nodeovermit
error: the server doesn't have a resource type "nodeovermit"
root@VM-0-12-ubuntu:/home/ubuntu# kubectl get NodeOvercommitConfig
NAME              OVERCOMMITRATIO                SELECTOR
overcommit-demo   {"cpu":"2.5","memory":"2.5"}   overcommit-demo

[googs1025]

root@VM-0-12-ubuntu:/home/ubuntu# kubectl get pod -o wide |grep busybox-deployment-overcommit |awk '{print $3}' |sort |uniq -c
     17 Pending
      3 Running

[googs1025]

生效了一下 这就是产生作用了是吗

[WangZzzhe]

生效了一下 这就是产生作用了是吗

@googs1025 观察node status，可用资源发生变化了就是生效了

[googs1025]

你们内存这种也支持吗 还是只有cpu 这种内存这种也支持 会不会造成oom呢

[WangZzzhe]

你们内存这种也支持吗 还是只有cpu 这种内存这种也支持 会不会造成oom呢

NAME              OVERCOMMITRATIO                SELECTOR
overcommit-demo   {"cpu":"2.5","memory":"2.5"}   overcommit-demo

可以为cpu和memory独立配置，OOM无法完全避免，下个版本预计会支持预测与驱逐，尽量减少内存的竞争