From 03fec1ea901057ff0cffad931e14a06983fb9927 Mon Sep 17 00:00:00 2001 From: Marcelo Giles Date: Thu, 18 May 2023 16:16:25 -0700 Subject: [PATCH] Update reference links --- .../administer-cluster/kubeadm/configure-cgroup-driver.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 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 0053eb0a73d..f4308c2b0eb 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 @@ -20,8 +20,9 @@ You should be familiar with the Kubernetes The [Container runtimes](/docs/setup/production-environment/container-runtimes) page explains that the `systemd` driver is recommended for kubeadm based setups instead -of the kubelet's [default `cgroupfs` driver](/docs/reference/config-api/kubelet-config.v1beta1), -because kubeadm manages the kubelet as a systemd service. +of the kubelet's [default](/docs/reference/config-api/kubelet-config.v1beta1) `cgroupfs` driver, +because kubeadm manages the kubelet as a +[systemd service](/docs/setup/production-environment/tools/kubeadm/kubelet-integration). The page also provides details on how to set up a number of different container runtimes with the `systemd` driver by default. @@ -34,7 +35,7 @@ driver of the kubelet. {{< note >}} In v1.22 and later, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`, -`kubeadm` defaults it to `systemd`. +kubeadm defaults it to `systemd`. {{< /note >}} A minimal example of configuring the field explicitly: