diff --git a/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md b/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md index 78dce7cc5e3..e45aa8b69f5 100644 --- a/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md +++ b/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md @@ -295,6 +295,10 @@ During installation, RKE generates a config file named `kube_config_rancher-clus ## Part 12-Remove Default Certificates +**For those using a certificate signed by a recognized CA:** + +>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#whats-next). + By default, Rancher automatically generates self-signed certificates for itself after installation. However, since you've provided your own certificates, you must disable the certificates that Rancher generated for itself. **To Remove the Default Certificates:** diff --git a/content/rancher/v2.x/en/installation/ha-server-install/_index.md b/content/rancher/v2.x/en/installation/ha-server-install/_index.md index 320c904e5de..b356b585931 100644 --- a/content/rancher/v2.x/en/installation/ha-server-install/_index.md +++ b/content/rancher/v2.x/en/installation/ha-server-install/_index.md @@ -370,6 +370,10 @@ During installation, RKE generates a config file named `kube_config_rancher-clus ## Part 12-Remove Default Certificates +**For those using a certificate signed by a recognized CA:** + +>**Note:** If you're using a self-signed certificate, you don't have to complete this part. Continue to [What's Next?](#whats-next). + By default, Rancher automatically generates self-signed certificates for itself after installation. However, since you've provided your own certificates, you must disable the certificates that Rancher generated for itself. **To Remove the Default Certificates:** diff --git a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md index ab32fb94475..646116798d7 100644 --- a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md @@ -16,10 +16,12 @@ To upgrade Rancher 2.x running in a high availablity configuration, run an upgra 2. Enter the following command: ``` -kubectl --kubeconfig=kube_config-rancher-cluster.yml set image deployment/cattle cattle-server=rancher/rancher:{{< tag_latest >}} -n cattle-system +kubectl --kubeconfig=kube_config-rancher-cluster.yml set image deployment/cattle cattle-server=rancher/rancher: -n cattle-system ``` -**Step Result:** The upgrade begins. Rancher Server may be unavailable for a few minutes. + Replace `` with the version that you want to upgrade to. For a list of tags available, see [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/). + + **Step Result:** The upgrade begins. Rancher Server may be unavailable for a few minutes. 3. Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window. -**Result:** Your Rancher Servers are upgraded to {{< tag_latest >}}. +**Result:** Your Rancher Servers are upgraded. diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md index d3f743042a2..c082e606fa0 100644 --- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md @@ -5,6 +5,8 @@ draft: true --- To upgrade Rancher Server 2.x to the latest version, you need to enter only a few commands. +>**Prerequisite:** Open Rancher and write down the version number displayed in the lower-left of the browser (example: `v2.0.0`). You'll need this number during the upgrade process. + 1. Stop the container currently running Rancher Server. Replace `` with the ID of your Rancher container. ``` @@ -15,6 +17,9 @@ docker stop 2. Create a `rancher-data` container. This container backs up the data from your current Rancher Server, which you'll restore in step 4. + - Replace `` with the same ID from the previous step. + - Replace `` with the version of Rancher that you are currently running, as mentioned in the **Rrerequisite** above. + ``` docker create --volumes-from \ --name rancher-data rancher/rancher: @@ -23,8 +28,11 @@ docker create --volumes-from \ 3. Pull the most recent image of Rancher. ``` -docker pull rancher/rancher:latest +docker pull rancher/rancher: ``` + + Replace `` with the version that you want to upgrade to. For a list of tags available, see [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/). + 4. Launch a new Rancher Server container using the `rancher-data` container. ``` @@ -42,4 +50,4 @@ docker run -d --volumes-from rancher-data --restart=unless-stopped \ 6. Log into Rancher. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window. -**Result:** Rancher server is upgraded to the latest version. +**Result:** Rancher Server is upgraded to the latest version.