From 5f4fa222599836232ba9091bc1cae400a77d1f74 Mon Sep 17 00:00:00 2001 From: Marlow Weston Date: Tue, 10 Oct 2023 01:54:22 -0500 Subject: [PATCH] Small mistake between sections of the document (#42089) * Small mistake between sections of the document The note for --kube-reserved-cgroup should match formatting for --system-reserved-cgroup. This changes helps those match. * Update reserve-compute-resources.md --------- Co-authored-by: Qiming Teng --- .../docs/tasks/administer-cluster/reserve-compute-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 66c0fc8f2c655..fedc88f2b2757 100644 --- a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md +++ b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md @@ -96,7 +96,7 @@ 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. With `systemd` +exist. The kubelet will fail to start 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.