whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #6475 from scjane/patch-15

Browse Source 
Update cpu-management-policies.md
This commit is contained in:
Qiming
2017-11-29 12:26:04 +08:00
committed by GitHub
parent 26a2b23afe a22f93bbbb
commit c5cafd7986
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/cpu-management-policies.md
+2 -2
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.