From a22f93bbbb6db3fcbda9341101d555734ffa5999 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Wed, 29 Nov 2017 10:31:42 +0800 Subject: [PATCH] Update cpu-management-policies.md --- docs/tasks/administer-cluster/cpu-management-policies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/cpu-management-policies.md b/docs/tasks/administer-cluster/cpu-management-policies.md index 83761d5e11..1f6b7ec69d 100644 --- a/docs/tasks/administer-cluster/cpu-management-policies.md +++ b/docs/tasks/administer-cluster/cpu-management-policies.md @@ -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.