From 4bf6c31e4e1e66761a087671c5aa1a0ae59f4b44 Mon Sep 17 00:00:00 2001 From: Pierre Tessier Date: Tue, 22 Dec 2020 21:14:32 -0500 Subject: [PATCH] remove misleading instructions There is no need to restart the kubelet as part of configuring kubeadm to set the cgroup driver. At this point in the setup instructions, the kubernetes cluster isn't even up and running yet, as kubeadm init hasn't been run. The previous step even says the kubelet is in a crashloop waiting for kubeadm. --- .../tools/kubeadm/install-kubeadm.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md index fc93d46cd2..52e903fecf 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md @@ -304,13 +304,6 @@ or `/etc/default/kubelet`(`/etc/sysconfig/kubelet` for RPMs), please remove it a (stored in `/var/lib/kubelet/config.yaml` by default). {{< /note >}} -Restarting the kubelet is required: - -```bash -sudo systemctl daemon-reload -sudo systemctl restart kubelet -``` - The automatic detection of cgroup driver for other container runtimes like CRI-O and containerd is work in progress.