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

Remove reference of unsupported k8s versions for CPUManager. (#17330) 

* Remove reference of unsupported k8s versions for CPUManager.

* Update note for none-policy and add links.

* Remove redundant note for alpha version.
pull/17543/head
Mitesh Jain 2019-11-12 14:34:07 +05:30 committed by Kubernetes Prow Robot
parent f54a7ad16f
commit f222648ebf
1 changed files with 3 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
content/en/docs/tasks/administer-cluster/cpu-management-policies.md
View File

@ -9,7 +9,7 @@ content_template: templates/task
{{% capture overview %}} {{% capture overview %}}
{{< feature-state state="beta" >}} {{< feature-state for_k8s_version="v1.12" state="beta" >}}
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
@ -44,14 +44,11 @@ management policies to determine some placement preferences on the node.
### Configuration ### Configuration
The CPU Manager is an alpha feature in Kubernetes v1.8. It was enabled by
default as a beta feature since v1.10.
The CPU Manager policy is set with the `--cpu-manager-policy` kubelet The CPU Manager policy is set with the `--cpu-manager-policy` kubelet
option. There are two supported policies: option. There are two supported policies:
* `none`: the default, which represents the existing scheduling behavior. * [`none`](#none-policy): the default policy.
* `static`: allows pods with certain resource characteristics to be * [`static`](#static-policy): allows pods with certain resource characteristics to be
granted increased CPU affinity and exclusivity on the node. granted increased CPU affinity and exclusivity on the node.
The CPU manager periodically writes resource updates through the CRI in The CPU manager periodically writes resource updates through the CRI in
@ -78,11 +75,6 @@ using the [cpuset cgroup controller](https://www.kernel.org/doc/Documentation/cg
System services such as the container runtime and the kubelet itself can continue to run on these exclusive CPUs.  The exclusivity only extends to other pods. System services such as the container runtime and the kubelet itself can continue to run on these exclusive CPUs.  The exclusivity only extends to other pods.
{{< /note >}} {{< /note >}}
{{< note >}}
The alpha version of this policy does not guarantee static
exclusive allocations across Kubelet restarts.
{{< /note >}}
{{< note >}} {{< note >}}
CPU Manager doesn't support offlining and onlining of CPU Manager doesn't support offlining and onlining of
CPUs at runtime. Also, if the set of online CPUs changes on the node, CPUs at runtime. Also, if the set of online CPUs changes on the node,