Update cpu-management-policies.md
This commit is contained in:
@@ -8,7 +8,7 @@ title: Control CPU Management Policies on the Node
|
||||
Kubernetes keeps many aspects of how pods execute on nodes abstracted
|
||||
from the user. This is by design. However, some workloads require
|
||||
stronger guarantees in terms of latency and/or performance in order to operate
|
||||
acceptably. The kubelet provides methods to enable more complex workload
|
||||
acceptably. The kubelet provides methods to enable more complex workload
|
||||
placement policies while keeping the abstraction free from explicit placement
|
||||
directives.
|
||||
|
||||
@@ -188,5 +188,5 @@ spec:
|
||||
This pod runs in the `Guaranteed` QoS class because only `limits` are specified
|
||||
and `requests` are set equal to `limits` when not explicitly specified. And the
|
||||
container's resource limit for the CPU resource is an integer greater than or
|
||||
equal to one.The `nginx` container is granted 2 exclusive CPUs.
|
||||
equal to one. The `nginx` container is granted 2 exclusive CPUs.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user