mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-14 04:57:13 +00:00
Fix typo and add restarting pods info
This commit is contained in:
committed by
Denise Schannon
parent
7f9e44164d
commit
381041cafa
+1
-1
@@ -8,7 +8,7 @@ _Available as of v2.2.0_
|
||||
By default, Kubernetes clusters require certificates and Rancher launched Kubernetes clusters have certificates automatically generated for them.
|
||||
|
||||
> **Note:** Even though the RKE CLI can use custom certificates for the Kubernetes cluster components, Rancher currently doesn't allow the ability to upload these in Rancher Launched Kubernetes clusters.
|
||||
hen generating certificates, the cluster certificates are set to expire after 1 year and the CA certificate expires after 10 years. Rotating these certificates are important before the certificates expire as well as if a certificate is compromised.
|
||||
When generating certificates, the cluster certificates are set to expire after 1 year and the CA certificate expires after 10 years. Rotating these certificates are important before the certificates expire as well as if a certificate is compromised.
|
||||
|
||||
After the certificates are rotated, the Kubernetes components are automatically restarted. Certificates can be rotated for the following services:
|
||||
|
||||
|
||||
@@ -101,3 +101,9 @@ INFO[0001] [certificates] Generating etcd-zzzzz certificate and key
|
||||
INFO[0001] Successfully Deployed state file at [./cluster.rkestate]
|
||||
INFO[0001] Rebuilding Kubernetes cluster with rotated certificates
|
||||
```
|
||||
|
||||
Rotating the CA certificate will also result in restarting some system pods to use the new CA certificate, this includes:
|
||||
|
||||
- Networking pods (canal, calico, flannel, and weave).
|
||||
- Ingress Controller pods.
|
||||
- KubeDNS pods.
|
||||
|
||||
Reference in New Issue
Block a user