From 1f494b71ae5575814502ae0d2f0aefe9ef5a0ecb Mon Sep 17 00:00:00 2001
From: dkeightley <derek@rancher.com>
Date: Wed, 15 Apr 2020 11:27:34 +1200
Subject: [PATCH] Add note around tls-ca taking effect at Rancher pod start

---
 .../rancher/v2.x/en/installation/options/tls-secrets/_index.md  | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/rancher/v2.x/en/installation/options/tls-secrets/_index.md b/content/rancher/v2.x/en/installation/options/tls-secrets/_index.md
index 76262c0a12f..72abc4d458a 100644
--- a/content/rancher/v2.x/en/installation/options/tls-secrets/_index.md
+++ b/content/rancher/v2.x/en/installation/options/tls-secrets/_index.md
@@ -31,3 +31,5 @@ Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to cre
 kubectl -n cattle-system create secret generic tls-ca \
   --from-file=cacerts.pem
 ```
+
+> **Note:** The configured `tls-ca` secret is retrieved when Rancher starts, on a running Rancher installation the updated CA will take effect after new Rancher pods are started.