From 80a3bba82d75b99c15cb3f25e0e6064adc6b6d2c Mon Sep 17 00:00:00 2001 From: Shaw Ho Date: Mon, 20 Jun 2022 17:25:42 +0800 Subject: [PATCH] Update reserve-compute-resources.md Add suffix '.slice' with `systemd` cgroup driver on reserved cgroup name. --- .../administer-cluster/reserve-compute-resources.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md index 8922a2fe00..f391227903 100644 --- a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md +++ b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md @@ -95,7 +95,10 @@ system daemon should ideally run within its own child control group. Refer to for more details on recommended control group hierarchy. Note that Kubelet **does not** create `--kube-reserved-cgroup` if it doesn't -exist. Kubelet will fail if an invalid cgroup is specified. +exist. Kubelet will fail if an invalid cgroup is specified. With `systemd` +cgroup driver, you should follow a specific pattern for the name of the cgroup you +define: the name should be the value you set for `--kube-reserved-cgroup`, +with `.slice` appended. ### System Reserved @@ -120,7 +123,10 @@ It is recommended that the OS system daemons are placed under a top level control group (`system.slice` on systemd machines for example). Note that `kubelet` **does not** create `--system-reserved-cgroup` if it doesn't -exist. `kubelet` will fail if an invalid cgroup is specified. +exist. `kubelet` will fail if an invalid cgroup is specified. With `systemd` +cgroup driver, you should follow a specific pattern for the name of the cgroup you +define: the name should be the value you set for `--system-reserved-cgroup`, +with `.slice` appended. ### Explicitly Reserved CPU List