kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update cpu-management-policies.md

This commit is contained in:
Wang Jie 2017-11-29 10:31:42 +08:00 committed by GitHub
parent aa2fe57460
commit a22f93bbbb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tasks/administer-cluster/cpu-management-policies.md
View File

@ -8,7 +8,7 @@ title: Control CPU Management Policies on the Node
Kubernetes keeps many aspects of how pods execute on nodes abstracted Kubernetes keeps many aspects of how pods execute on nodes abstracted
from the user. This is by design.  However, some workloads require from the user. This is by design.  However, some workloads require
stronger guarantees in terms of latency and/or performance in order to operate 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 placement policies while keeping the abstraction free from explicit placement
directives. directives.
@ -188,5 +188,5 @@ spec:
This pod runs in the `Guaranteed` QoS class because only `limits` are specified 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 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 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.