From 240e91844e8ddd286271b0b02525fd35ede320f1 Mon Sep 17 00:00:00 2001 From: Ismo Puustinen Date: Wed, 1 Aug 2018 01:09:39 +0300 Subject: [PATCH] Add a note CPU change handling in CPU manager. (#9671) This relates to PR https://github.com/kubernetes/kubernetes/pull/66718 which validates that CPU manager state and current set CPUs are in sync. --- .../tasks/administer-cluster/cpu-management-policies.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md index 0dd23ad78c..18ba1f3700 100644 --- a/content/en/docs/tasks/administer-cluster/cpu-management-policies.md +++ b/content/en/docs/tasks/administer-cluster/cpu-management-policies.md @@ -84,6 +84,13 @@ using the [cpuset cgroup controller](https://www.kernel.org/doc/Documentation/cg exclusive allocations across Kubelet restarts. {{< /note >}} +{{< note >}} +**Note:** CPU Manager doesn't support offlining and onlining of +CPUs at runtime. Also, if the set of online CPUs changes on the node, +the node must be drained and CPU manager manually reset by deleting the +state file `cpu_manager_state` in the kubelet root directory. +{{< /note >}} + This policy manages a shared pool of CPUs that initially contains all CPUs in the node. The amount of exclusively allocatable CPUs is equal to the total number of CPUs in the node minus any CPU reservations by the kubelet `--kube-reserved` or