Clarify that burstable pods also have their limit enforced by CFS quota

This commit is contained in:
Wesley Williams
2021-07-16 18:10:38 +01:00
parent cc9011a42c
commit 723b94de50
2 changed files with 4 additions and 2 deletions
@@ -63,7 +63,8 @@ duration as `--node-status-update-frequency`.
The `none` policy explicitly enables the existing default CPU The `none` policy explicitly enables the existing default CPU
affinity scheme, providing no affinity beyond what the OS scheduler does affinity scheme, providing no affinity beyond what the OS scheduler does
automatically.  Limits on CPU usage for automatically.  Limits on CPU usage for
[Guaranteed pods](/docs/tasks/configure-pod-container/quality-service-pod/) [Guaranteed pods](/docs/tasks/configure-pod-container/quality-service-pod/) and
[Burstable pods](/docs/tasks/configure-pod-container/quality-service-pod/)
are enforced using CFS quota. are enforced using CFS quota.
### Static policy ### Static policy
@@ -94,7 +94,8 @@ CPU 管理器定期通过 CRI 写入资源更新,以保证内存中 CPU 分配
The `none` policy explicitly enables the existing default CPU The `none` policy explicitly enables the existing default CPU
affinity scheme, providing no affinity beyond what the OS scheduler does affinity scheme, providing no affinity beyond what the OS scheduler does
automatically.  Limits on CPU usage for automatically.  Limits on CPU usage for
[Guaranteed pods](/docs/tasks/configure-pod-container/quality-service-pod/) [Guaranteed pods](/docs/tasks/configure-pod-container/quality-service-pod/) and
[Burstable pods](/docs/tasks/configure-pod-container/quality-service-pod/)
are enforced using CFS quota. are enforced using CFS quota.
--> -->
### none 策略 ### none 策略