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

added placeholders in upgrade commands

Browse Source
This commit is contained in:
Mark Bishop
2018-05-18 14:56:26 -07:00
committed by Mark Bishop
parent cef915cae6
commit e10a6d39d7
4 changed files with 23 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md
+4
View File
@@ -295,6 +295,10 @@ During installation, RKE generates a config file named `kube_config_rancher-clus
## Part 12-Remove Default Certificates ## 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. 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:** **To Remove the Default Certificates:**
content/rancher/v2.x/en/installation/ha-server-install/_index.md
+4
View File
@@ -370,6 +370,10 @@ During installation, RKE generates a config file named `kube_config_rancher-clus
## Part 12-Remove Default Certificates ## 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. 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:** **To Remove the Default Certificates:**
content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md
+5 -3
View File
@@ -16,10 +16,12 @@ To upgrade Rancher 2.x running in a high availablity configuration, run an upgra
2. Enter the following command: 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:<VERSION_TAG> -n cattle-system
``` ```
**Step Result:** The upgrade begins. Rancher Server may be unavailable for a few minutes. Replace `<VERSION_TAG>` 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. 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.
content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
+10 -2
View File
@@ -5,6 +5,8 @@ draft: true
--- ---
To upgrade Rancher Server 2.x to the latest version, you need to enter only a few commands. 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 `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container. 1. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
``` ```
@@ -15,6 +17,9 @@ docker stop <RANCHER_CONTAINER_ID>
2. Create a `rancher-data` container. This container backs up the data from your current Rancher Server, which you'll restore in step 4. 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 `<RANCHER_CONTAINER_ID>` with the same ID from the previous step.
- Replace `<RANCHER_CONTAINER_TAG>` with the version of Rancher that you are currently running, as mentioned in the **Rrerequisite** above.
``` ```
docker create --volumes-from <RANCHER_CONTAINER_ID> \ docker create --volumes-from <RANCHER_CONTAINER_ID> \
--name rancher-data rancher/rancher:<RANCHER_CONTAINER_TAG> --name rancher-data rancher/rancher:<RANCHER_CONTAINER_TAG>
@@ -23,8 +28,11 @@ docker create --volumes-from <RANCHER_CONTAINER_ID> \
3. Pull the most recent image of Rancher. 3. Pull the most recent image of Rancher.
``` ```
docker pull rancher/rancher:latest docker pull rancher/rancher:<VERSION_TAG>
``` ```
Replace `<VERSION_TAG>` 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. 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. 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.