From 01bbc1ce80a49fe9dfebdb6f777047c504357cc8 Mon Sep 17 00:00:00 2001 From: Adam Herrington Date: Tue, 30 Apr 2019 11:37:11 -0500 Subject: [PATCH] Same CA note when replacing certificates only applies when certificate is a private CA signed certificate --- .../v2.x/en/installation/ha/helm-rancher/tls-secrets/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/_index.md b/content/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/_index.md index 98d8199aee6..2866ca911e5 100644 --- a/content/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/_index.md +++ b/content/rancher/v2.x/en/installation/ha/helm-rancher/tls-secrets/_index.md @@ -15,7 +15,7 @@ kubectl -n cattle-system create secret tls tls-rancher-ingress \ --key=tls.key ``` -> **Note:** If you want to replace the certificate, you can delete the `tls-rancher-ingress` secret using `kubectl -n cattle-system delete secret tls-rancher-ingress` and add a new one using the command shown above. Replacing the certificate is only supported if the new certificate is signed by the same CA as the certificate currently in use. +> **Note:** If you want to replace the certificate, you can delete the `tls-rancher-ingress` secret using `kubectl -n cattle-system delete secret tls-rancher-ingress` and add a new one using the command shown above. If you are using a private CA signed certificate, replacing the certificate is only possible if the new certificate is signed by the same CA as the certificate currently in use. ### Using a Private CA Signed Certificate