public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-24 20:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rewording the amendment of v2.5 & 2.6 CA documentation

Browse Source
This commit is contained in:
divya-mohan0209
2022-03-07 17:32:52 +05:30
parent 0cefcedccd
commit 6e36eaaadf
2 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
+10
View File
@@ -13,6 +13,7 @@ A summary of the steps is as follows:
2. Create or update the `tls-ca` Kubernetes secret resource with the root CA certificate (only required when using a private CA).
3. Update the Rancher installation using the Helm CLI.
4. Reconfigure the Rancher agents to trust the new CA certificate.
5. Select Force Update of fleet clusters to connect fleet-agent to Rancher
The details of these instructions are below.
@@ -145,3 +146,12 @@ First, generate the agent definitions as described here: https://gist.github.com
Then, connect to a controlplane node of the downstream cluster via SSH, create a Kubeconfig and apply the definitions:
https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b
# 5. Select Force Update of fleet clusters to connect fleet-agent to Rancher
Select 'Force Update' for the clusters within the Continuous Delivery view of the Rancher Explorer UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher.
### Why is this step required?
Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this needs to be updated for a successful connection of the fleet-agent to Rancher.
content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md
+9
View File
@@ -11,6 +11,7 @@ A summary of the steps is as follows:
2. Create or update the `tls-ca` Kubernetes secret resource with the root CA certificate (only required when using a private CA).
3. Update the Rancher installation using the Helm CLI.
4. Reconfigure the Rancher agents to trust the new CA certificate.
5. Select Force Update of fleet clusters to connect fleet-agent to Rancher
The details of these instructions are below.
@@ -143,3 +144,11 @@ First, generate the agent definitions as described here: https://gist.github.com
Then, connect to a controlplane node of the downstream cluster via SSH, create a Kubeconfig and apply the definitions:
https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b
# 5. Select Force Update of fleet clusters to connect fleet-agent to Rancher
Select 'Force Update' for the clusters within the Continuous Delivery view of the Rancher Explorer UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher.
### Why is this step required?
Fleet agents in Rancher managed clusters store kubeconfig that is used to connect to the Rancher proxied kube-api in the fleet-agent secret of the fleet-system namespace. The kubeconfig contains a certificate-authority-data block containing the Rancher CA. When changing the Rancher CA, this needs to be updated for a successful connection of the fleet-agent to Rancher.