Merge pull request #28978 from wesleyw72/cpu-management-burstable-cfs

Clarify that burstable pods also have their limit enforced by CFS quota
This commit is contained in:
Kubernetes Prow Robot
2021-08-15 03:39:46 -07:00
committed by GitHub
@@ -66,7 +66,8 @@ The flag takes a comma-separated list of `key=value` policy options.
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