From 15f0b81debba68c390b83b4ee438df7917a42c49 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Mon, 7 Mar 2022 17:01:20 +0530 Subject: [PATCH 01/12] Amendments to Cluster provisioning and registering documentation --- .../registered-clusters/_index.md | 13 ++++---- suggesting-an-improvement.md | 33 +++++++++++++++++++ 2 files changed, 39 insertions(+), 7 deletions(-) create mode 100644 suggesting-an-improvement.md diff --git a/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md b/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md index 4d9ab0c2a1f..cdcbc76e1a1 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md @@ -3,7 +3,7 @@ title: Registering Existing Clusters weight: 6 --- -The cluster registration feature replaced the feature to import clusters. +Along with importing clusters, as of v2.5, Rancher allows you to tie in closer with cloud APIs and manage your cluster by registering existing clusters. The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see [Management Capabilities for Registered Clusters.](#management-capabilities-for-registered-clusters) @@ -168,7 +168,7 @@ Also in the K3s documentation, nodes with the worker role are called agent nodes # Debug Logging and Troubleshooting for Registered K3s Clusters -Nodes are upgraded by the system upgrade controller running in the downstream cluster. Based on the cluster configuration, Rancher deploys two [plans](https://github.com/rancher/system-upgrade-controller#example-upgrade-plan) to upgrade K3s nodes: one for controlplane nodes and one for workers. The system upgrade controller follows the plans and upgrades the nodes. +Nodes are upgraded by the system upgrade controller running in the downstream cluster. Based on the cluster configuration, Rancher deploys two [plans](https://github.com/rancher/system-upgrade-controller#example-upgrade-plan) to upgrade K3s nodes: one for controlplane nodes and one for workers. The system upgrade controller follows the plans and upgrades the nodes. To enable debug logging on the system upgrade controller deployment, edit the [configmap](https://github.com/rancher/system-upgrade-controller/blob/50a4c8975543d75f1d76a8290001d87dc298bdb4/manifests/system-upgrade-controller.yaml#L32) to set the debug environment variable to true. Then restart the `system-upgrade-controller` pod. @@ -196,7 +196,7 @@ Authorized Cluster Endpoint (ACE) support has been added for registered RKE2 and > **Note:** > -> - These steps only need to be performed on the control plane nodes of the downstream cluster. You must configure each control plane node individually. +> - These steps only need to be performed on the control plane nodes of the downstream cluster. You must configure each control plane node individually. > > - The following steps will work on both RKE2 and K3s clusters registered in v2.6.x as well as those registered (or imported) from a previous version of Rancher with an upgrade to v2.6.x. > @@ -223,19 +223,19 @@ Authorized Cluster Endpoint (ACE) support has been added for registered RKE2 and context: user: Default cluster: Default - + 1. Add the following to the config file (or create one if it doesn’t exist); note that the default location is `/etc/rancher/{rke2,k3s}/config.yaml`: kube-apiserver-arg: - authentication-token-webhook-config-file=/var/lib/rancher/{rke2,k3s}/kube-api-authn-webhook.yaml - + 1. Run the following commands: sudo systemctl stop {rke2,k3s}-server sudo systemctl start {rke2,k3s}-server 1. Finally, you **must** go back to the Rancher UI and edit the imported cluster there to complete the ACE enablement. Click on **⋮ > Edit Config**, then click the **Networking** tab under Cluster Configuration. Finally, click the **Enabled** button for **Authorized Endpoint**. Once the ACE is enabled, you then have the option of entering a fully qualified domain name (FQDN) and certificate information. - + >**Note:** The FQDN field is optional, and if one is entered, it should point to the downstream cluster. Certificate information is only needed if there is a load balancer in front of the downstream cluster that is using an untrusted certificate. If you have a valid certificate, then nothing needs to be added to the CA Certificates field. # Annotating Registered Clusters @@ -286,4 +286,3 @@ To annotate a registered cluster, 1. Click **Save**. **Result:** The annotation does not give the capabilities to the cluster, but it does indicate to Rancher that the cluster has those capabilities. - diff --git a/suggesting-an-improvement.md b/suggesting-an-improvement.md new file mode 100644 index 00000000000..c243c72b006 --- /dev/null +++ b/suggesting-an-improvement.md @@ -0,0 +1,33 @@ +# Suggesting an improvement + +If you notice an issue with Kubewarden documentation or want to suggest new content, then open an issue. You only require access to a [GitHub account](https://github.com/join) and a browser. + +In most cases, any new documentation work for Kubewarden begins with an issue in GitHub. The [documentation team for Kubewarden](https://github.com/orgs/kubewarden/teams/kubewarden-documentation) reviews, categorizes and tags them as appropriate. Everybody is welcome to work on the issue, including the reporter, but we request that you assign it to yourself before commencing any work to avoid duplicate efforts. + +## Opening an issue + +If you want to suggest improvements to existing documentation content or notice an error, then open an issue. + +- Click the GitHub Octocat icon on the top. This redirects you to the [documentation repository for Kubewarden](https://github.com/kubewarden/docs). +- Navigate to the Issues tab and click **New issue**. +- Describe the issue or suggestion for improvement. The more details you provide, the better! +- Click Submit new issue. +- Post submitting, you can either assign it to yourself or wait for a community member to pick it up. Members of the documentation team and from the community might request clarifications before they can take action on your issue, so we'd request you to actively check your issue or [turn on GitHub notifications](https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications). + +## New content suggestions + +If you want to suggest new content, please file an issue following the steps above. Either + +- You can choose an existing page in the section you think the content belongs in and click Create an issue. +OR +- Navigate to [GitHub](https://github.com/kubewarden/docs/issues/new/choose) and file the issue directly. + +## How do I make my contribution count? + +No contribution is big or small! However, to ensure that the community derives maximum value we'd request you to follow the below when reporting an issue: + +- Focus on providing a clear description of the issue. Some key points to consider would be specifically describing what is missing, outdated, erroneous, or requires qualitative/technical improvement. +- Detailing the specific impact the issue has on users. +- Delimiting the scope of the issue. If the scope is larger, we'd request you to break it down to smaller tasks within an issue. For example, "Creating a Contribution guide" is very widely scoped since there would be multiple tasks associated with the issue. However, "Fixing grammatical error on the Quickstart page" is a more narrowly scoped issue that would, potentially, require only a single pull request. +- Crosscheck existing issues to avoid duplicate work. +- There is a fair chance that you're opening an issue with reference to another pull request or existing issue. Ensure you reference it in the issue you're opening to provide context for contributors who may want to work on it. From 0cefcedccda62c3bab7db44a185ac2b41f570289 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Mon, 7 Mar 2022 17:17:50 +0530 Subject: [PATCH 02/12] Adding change to the registereing cluster docs --- suggesting-an-improvement.md | 33 --------------------------------- 1 file changed, 33 deletions(-) delete mode 100644 suggesting-an-improvement.md diff --git a/suggesting-an-improvement.md b/suggesting-an-improvement.md deleted file mode 100644 index c243c72b006..00000000000 --- a/suggesting-an-improvement.md +++ /dev/null @@ -1,33 +0,0 @@ -# Suggesting an improvement - -If you notice an issue with Kubewarden documentation or want to suggest new content, then open an issue. You only require access to a [GitHub account](https://github.com/join) and a browser. - -In most cases, any new documentation work for Kubewarden begins with an issue in GitHub. The [documentation team for Kubewarden](https://github.com/orgs/kubewarden/teams/kubewarden-documentation) reviews, categorizes and tags them as appropriate. Everybody is welcome to work on the issue, including the reporter, but we request that you assign it to yourself before commencing any work to avoid duplicate efforts. - -## Opening an issue - -If you want to suggest improvements to existing documentation content or notice an error, then open an issue. - -- Click the GitHub Octocat icon on the top. This redirects you to the [documentation repository for Kubewarden](https://github.com/kubewarden/docs). -- Navigate to the Issues tab and click **New issue**. -- Describe the issue or suggestion for improvement. The more details you provide, the better! -- Click Submit new issue. -- Post submitting, you can either assign it to yourself or wait for a community member to pick it up. Members of the documentation team and from the community might request clarifications before they can take action on your issue, so we'd request you to actively check your issue or [turn on GitHub notifications](https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications). - -## New content suggestions - -If you want to suggest new content, please file an issue following the steps above. Either - -- You can choose an existing page in the section you think the content belongs in and click Create an issue. -OR -- Navigate to [GitHub](https://github.com/kubewarden/docs/issues/new/choose) and file the issue directly. - -## How do I make my contribution count? - -No contribution is big or small! However, to ensure that the community derives maximum value we'd request you to follow the below when reporting an issue: - -- Focus on providing a clear description of the issue. Some key points to consider would be specifically describing what is missing, outdated, erroneous, or requires qualitative/technical improvement. -- Detailing the specific impact the issue has on users. -- Delimiting the scope of the issue. If the scope is larger, we'd request you to break it down to smaller tasks within an issue. For example, "Creating a Contribution guide" is very widely scoped since there would be multiple tasks associated with the issue. However, "Fixing grammatical error on the Quickstart page" is a more narrowly scoped issue that would, potentially, require only a single pull request. -- Crosscheck existing issues to avoid duplicate work. -- There is a fair chance that you're opening an issue with reference to another pull request or existing issue. Ensure you reference it in the issue you're opening to provide context for contributors who may want to work on it. From 6e36eaaadf8be26de24e1b6cecdc3502692dce9a Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Mon, 7 Mar 2022 17:32:52 +0530 Subject: [PATCH 03/12] Rewording the amendment of v2.5 & 2.6 CA documentation --- .../en/installation/resources/update-ca-cert/_index.md | 10 ++++++++++ .../en/installation/resources/update-ca-cert/_index.md | 9 +++++++++ 2 files changed, 19 insertions(+) diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md index c256f9f5905..08c26328652 100644 --- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md @@ -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. diff --git a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md index 5a7a477fa82..658ffc2ea34 100644 --- a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md @@ -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. From e6f414711c3b4f9d1f4fe6e909e86187dbc75b6a Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 16:23:41 +0530 Subject: [PATCH 04/12] Modifying content for v2.5 and 2.6 CA certificate content --- .../v2.6/en/cluster-provisioning/registered-clusters/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md b/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md index cdcbc76e1a1..35146cafedd 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/registered-clusters/_index.md @@ -3,7 +3,7 @@ title: Registering Existing Clusters weight: 6 --- -Along with importing clusters, as of v2.5, Rancher allows you to tie in closer with cloud APIs and manage your cluster by registering existing clusters. +The cluster registration feature replaced the feature to import clusters. The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see [Management Capabilities for Registered Clusters.](#management-capabilities-for-registered-clusters) From 5800f6da0a8cb7e090f4d05427a7157ef4c05d47 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:52:03 +0530 Subject: [PATCH 05/12] Update content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.5/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md index 08c26328652..7a3b3e9413b 100644 --- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md @@ -150,7 +150,7 @@ 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. +Select 'Force Update' for the clusters within the [Continuous Delivery]({{}}/rancher/v2.5/en/deploy-across-clusters/fleet/#accessing-fleet-in-the-rancher-ui) view under Cluster Explorer in the Rancher UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher. ### Why is this step required? From be250166d22a8ac92099047eeac7378022a0ac83 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:52:20 +0530 Subject: [PATCH 06/12] Update content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.5/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md index 7a3b3e9413b..ee6457aeefb 100644 --- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md @@ -13,7 +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 +5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher. The details of these instructions are below. From 4ed4c8ee202eb21d2541da2cfe7517b2d826a4c1 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:52:34 +0530 Subject: [PATCH 07/12] Update content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.5/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md index ee6457aeefb..5b8e5f7b256 100644 --- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md @@ -148,7 +148,7 @@ Then, connect to a controlplane node of the downstream cluster via SSH, create a https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b -# 5. Select Force Update of fleet clusters to connect fleet-agent to Rancher +# 5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher Select 'Force Update' for the clusters within the [Continuous Delivery]({{}}/rancher/v2.5/en/deploy-across-clusters/fleet/#accessing-fleet-in-the-rancher-ui) view under Cluster Explorer in the Rancher UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher. From 39596de19eb13291a33ac7b439b812e1ca3d0e89 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:52:54 +0530 Subject: [PATCH 08/12] Update content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.5/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md index 5b8e5f7b256..751feae2d8c 100644 --- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md @@ -154,4 +154,4 @@ Select 'Force Update' for the clusters within the [Continuous Delivery]({{ Date: Tue, 8 Mar 2022 20:53:05 +0530 Subject: [PATCH 09/12] Update content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.6/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md index 658ffc2ea34..1844c02f224 100644 --- a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md @@ -11,7 +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 +5. Select Force Update of Fleet clusters to connect fleet-agent to Rancher. The details of these instructions are below. From cef5df873db5995274d42d080fa218519a17a4dd Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:53:15 +0530 Subject: [PATCH 10/12] Update content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.6/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md index 1844c02f224..737c3160586 100644 --- a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md @@ -145,7 +145,7 @@ 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 +# 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. From 83f2ae662f1ee2ab2a095cd713d26cddf70284e4 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:53:29 +0530 Subject: [PATCH 11/12] Update content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.6/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md index 737c3160586..1e51027858c 100644 --- a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md @@ -147,7 +147,7 @@ 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. +Select 'Force Update' for the clusters within the [Continuous Delivery]({{}}/rancher/v2.6/en/deploy-across-clusters/fleet/#accessing-fleet-in-the-rancher-ui) view of the Rancher UI to allow the fleet-agent in downstream clusters to successfully connect to Rancher. ### Why is this step required? From 7bc69e96ca47a3cd0c876910ccbbe353de5412e0 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 8 Mar 2022 20:53:38 +0530 Subject: [PATCH 12/12] Update content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md Co-authored-by: Jen Travinski --- .../v2.6/en/installation/resources/update-ca-cert/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md index 1e51027858c..3c01e5f7eaf 100644 --- a/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md +++ b/content/rancher/v2.6/en/installation/resources/update-ca-cert/_index.md @@ -151,4 +151,4 @@ Select 'Force Update' for the clusters within the [Continuous Delivery]({{