From 68a17746563a1b1c8a877a96b1abf55ac922bc75 Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Fri, 11 Oct 2019 21:14:40 +0300 Subject: [PATCH] Update content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md Co-Authored-By: Tim Bannister --- .../en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 6c98dc7edb4c8..6591d8be7050d 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md @@ -86,7 +86,7 @@ If you have more complex requirements for certificate renewal, you can opt out f {{< warning >}} Prior to kubeadm version 1.17 there is a [bug](https://github.com/kubernetes/kubeadm/issues/1818) where the default value for `--certificate-renewal` is `false` for the `kubeadm upgrade node` -command, so the flag has to be passed explicitly `--certificate-renewal=true`. +command. In that case, you should explicitly set `--certificate-renewal=true`. {{< /warning >}} ## Manual certificate renewal