From a3f671a816d3ee65f3a62c48d65aee0cf260dce2 Mon Sep 17 00:00:00 2001 From: Oleg Butuzov Date: Tue, 12 Nov 2019 04:28:06 +0200 Subject: [PATCH] fix - broken link (#17529) Fix for brokenlink at kubeadm upgrade page https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/ (see link "certificate management documentation" ) --- .../en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md index da1d46de29..31c2f11d9c 100644 --- a/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md +++ b/content/en/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md @@ -25,7 +25,7 @@ To use kube-dns with upgrades in Kubernetes v1.13.0 and later please follow [thi In Kubernetes v1.15.0 and later, `kubeadm upgrade apply` and `kubeadm upgrade node` will also automatically renew the kubeadm managed certificates on this node, including those stored in kubeconfig files. To opt-out, it is possible to pass the flag `--certificate-renewal=false`. For more details about certificate -renewal see the [certificate management documentation](docs/tasks/administer-cluster/kubeadm/kubeadm-certs). +renewal see the [certificate management documentation](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs). {{< note >}} The commands `kubeadm upgrade apply` and `kubeadm upgrade plan` have a legacy `--config`