From 75b7fce11f17e89a8ccdb02f5809b8bf107f604c Mon Sep 17 00:00:00 2001 From: "paul.zhang" Date: Wed, 22 Jun 2022 17:28:48 +0800 Subject: [PATCH] Add anchor:#modify-kubelet-configmap Add anchor:#modify-kubelet-configmap --- .../administer-cluster/kubeadm/configure-cgroup-driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md index 97fa2bc352..8fa57ea894 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md @@ -73,7 +73,7 @@ To use `cgroupfs` and to prevent `kubeadm upgrade` from modifying the about its value. This applies to a case where you do not wish future versions of kubeadm to apply the `systemd` driver by default. -See the below section on "Modify the kubelet ConfigMap" for details on +See the below section on "[Modify the kubelet ConfigMap](#modify-kubelet-configmap)" for details on how to be explicit about the value. If you wish to configure a container runtime to use the `cgroupfs` driver, @@ -92,7 +92,7 @@ before joining the new nodes and ensuring the workloads can safely move to the n nodes before deleting the old nodes. {{< /note >}} -### Modify the kubelet ConfigMap +### Modify the kubelet ConfigMap {#modify-kubelet-configmap} - Call `kubectl edit cm kubelet-config -n kube-system`. - Either modify the existing `cgroupDriver` value or add a new field that looks like this: