From 380080774cc561c00eff7a0ac9204a3ff7f1f9e3 Mon Sep 17 00:00:00 2001 From: David Yu Date: Thu, 4 Feb 2021 09:44:04 -0800 Subject: [PATCH] docs: fix another broken link to upgrading k8s servers from token rotation page (#9707) fix another broken link to upgrading k8s servers from token rotation page --- website/content/docs/k8s/operations/certificate-rotation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/k8s/operations/certificate-rotation.mdx b/website/content/docs/k8s/operations/certificate-rotation.mdx index f52029187e..f520efef2e 100644 --- a/website/content/docs/k8s/operations/certificate-rotation.mdx +++ b/website/content/docs/k8s/operations/certificate-rotation.mdx @@ -12,7 +12,7 @@ are issued every time the Helm chart is upgraded. These certificates are signed continue to work as expected in the existing cluster. Consul servers read the certificates from Kubernetes secrets during start-up and keep them in memory. In order to ensure the -servers use the newer certificate, the server pods need to be [restarted explicitly](/docs/k8s/operations/upgrade#upgrading-consul-servers) in +servers use the newer certificate, the server pods need to be [restarted explicitly](/docs/k8s/upgrade#upgrading-consul-servers) in a situation where `helm upgrade` does not restart the server pods. To explicitly perform server certificate rotation, follow these steps: