From 1ad2bce47543b96e33ffe21f447694d672cf84ac Mon Sep 17 00:00:00 2001 From: Yuiko Mouri Date: Thu, 5 Aug 2021 14:55:29 +0900 Subject: [PATCH] Fix missing link --- .../en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md index b51f786f04..3d4959b536 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md @@ -133,8 +133,7 @@ dynamic certificate reload is currently not supported for all components and cer [Static Pods](/docs/tasks/configure-pod-container/static-pod/) are managed by the local kubelet and not by the API Server, thus kubectl cannot be used to delete and restart them. To restart a static Pod you can temporarily remove its manifest file from `/etc/kubernetes/manifests/` -and wait for 20 seconds (see the `fileCheckFrequency` value in [KubeletConfiguration struct](/docs/ -reference/config-api/kubelet-config.v1beta1/). +and wait for 20 seconds (see the `fileCheckFrequency` value in [KubeletConfiguration struct](/docs/reference/config-api/kubelet-config.v1beta1/). The kubelet will terminate the Pod if it's no longer in the manifest directory. You can then move the file back and after another `fileCheckFrequency` period, the kubelet will recreate the Pod and the certificate renewal for the component can complete.