From 40f525692455a114270133b4f5d970537956f8ce Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Wed, 20 Oct 2021 02:20:40 +0530 Subject: [PATCH] Notify deletion of Kubelet bootstrap token Kubeadm deletes the file `/etc/kubernetes/bootstrap-kubelet.conf` as per https://github.com/kubernetes/kubernetes/pull/80676 --- .../tools/kubeadm/kubelet-integration.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md b/content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md index dda9aba77a..bae9af6bbb 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md @@ -151,8 +151,10 @@ systemctl daemon-reload && systemctl restart kubelet After the kubelet loads the new configuration, kubeadm writes the `/etc/kubernetes/bootstrap-kubelet.conf` KubeConfig file, which contains a CA certificate and Bootstrap Token. These are used by the kubelet to perform the TLS Bootstrap and obtain a unique -credential, which is stored in `/etc/kubernetes/kubelet.conf`. When this file is written, the kubelet -has finished performing the TLS Bootstrap. +credential, which is stored in `/etc/kubernetes/kubelet.conf`. + +When the `/etc/kubernetes/kubelet.conf` file is written, the kubelet has finished performing the TLS Bootstrap. +Kubeadm deletes the `/etc/kubernetes/bootstrap-kubelet.conf` file after completing the TLS Bootstrap. ## The kubelet drop-in file for systemd