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

ha upgrade rewrite

Browse Source
This commit is contained in:
Mark Bishop
2018-05-17 18:37:58 -07:00
committed by Mark Bishop
parent cc1e307e60
commit 308ca5ae8e
3 changed files with 48 additions and 26 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
+10 -3
View File
@@ -51,9 +51,13 @@ This set of instructions creates a new Kubernetes cluster that's dedicated to ru
Run RKE to deploy Rancher to your cluster.
11. **For those using a certificate signed by a recognized CA:**
11. [Backup kube_config_rancher-cluster.yml](part-11-backup-kube-config-rancher-cluster-yml)
[Remove Default Certificates](#part-11-remove-default-certificates)
During installation, RKE generates a config file that you'll use later for upgrades. Back it up to a safe location.
12. **For those using a certificate signed by a recognized CA:**
[Remove Default Certificates](#part-12-remove-default-certificates)
If you chose [Option B](#option-b-bring-your-own-certificate-signed-by-recognized-ca) as your SSL option, log into the Rancher UI and remove the certificates that Rancher automatically generates.
@@ -284,8 +288,11 @@ INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
...
INFO[0101] Finished building Kubernetes cluster successfully
```
## Part 11—Backup kube_config_rancher-cluster.yml
## Part 11-Remove Default Certificates
During installation, RKE generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the RKE binary. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
## Part 12-Remove Default Certificates
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.
content/rancher/v2.x/en/installation/ha-server-install/_index.md
+24 -3
View File
@@ -51,6 +51,17 @@ This set of instructions creates a new Kubernetes cluster that's dedicated to ru
Run RKE to deploy Rancher to your cluster.
11. [Backup kube_config_rancher-cluster.yml](part-11-backup-kube-config-rancher-cluster-yml)
During installation, RKE generates a config file that you'll use later for upgrades. Back it up to a safe location.
12. **For those using a certificate signed by a recognized CA:**
[Remove Default Certificates](#part-12-remove-default-certificates)
If you chose [Option B](#option-b-bring-your-own-certificate-signed-by-recognized-ca) as your SSL option, log into the Rancher UI and remove the certificates that Rancher automatically generates.
## Part 1-Provision Linux Hosts
Before you install Rancher, confirm you meet the host requirements. Provision 3 new Linux hosts using the requirements below.
@@ -353,10 +364,20 @@ INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
INFO[0101] Finished building Kubernetes cluster successfully
```
## Part 11—Backup kube_config_rancher-cluster.yml
During installation, RKE generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the RKE binary. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
## Part 12-Remove Default Certificates
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:**
1. Log into Rancher.
2. Select **Settings** > **cacerts**.
3. Choose `Edit` and remove the contents. Then click `Save`.
## What's Next?
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#configure-dns).
>**Note:**
> If you are using certificate signed by a recognized CA (Option B from earlier), you must clear the `cacerts` value from the CA due to [GitHub Issue #11388](https://github.com/rancher/rancher/issues/11388). To complete this action, choose Settings > cacerts, choose Edit, remove the contents, and then click Save.
content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md
+14 -20
View File
@@ -3,29 +3,23 @@ title: High Availability Upgrade
weight: 1020
draft: true
---
To upgrade Rancher 2.x running in a high availablity configuration, download your cluster's Kubeconfig file and run an upgrade command.
To upgrade Rancher 2.x running in a high availablity configuration, move run an upgrade command that points to your upgrade config file.
1. Log into Rancher and browse to the cluster that your're using to run Rancher.
>**Prerequisites:**
>
>- Install [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) on your workstation.
>- Confirm that the following path exists on your workstation: `~/.kube/`. If it doesn't, create it yourself.
>- Copy `kube_config_rancher-cluster.yml`, which is automatically generated after [Rancher Server installation]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install#part-11-backup-kube-config-rancher-cluster-yml), to the `~/.kube/` directory.
2. From the cluster dashboard, click **Kubeconfig File**.
1. From your workstation, open **Terminal**.
**Step Result:** The Kubeconfig file opens in a new window.
2. Enter the following command:
3. Copy the YAML that's displayed to your clipboard. Then close the window.
4. From your workstation, create a new path of `~/.kube/config`. Open your home directory, create a directory named `.kube`, and then create a file named `config`.
5. Paste the contents of your clipboard in the empty `config` file and save.
6. From the cluster dashboard, click **Launch kubectl**.
>**Tip:** If you don't have kubectl, you can get it by clicking the Kubeconfig File button and selecting the Download link at the bottom of the window.
7. From the kubectl **Shell**, enter the following command:
```
kubectl set image deployment/cattle cattle-server=rancher/rancher:{{< tag_latest >}} -n cattle-system
```
8. Confirm that the upgrade succeeded by checking the version displayed in the bottom-left corner of the browser window.
kubectl --kubeconfig=kube_config-rancher-cluster.yml set image deployment/cattle cattle-server=rancher/rancher:{{< tag_latest >}} -n cattle-system
```
**Step Result:** The upgrade begins. Rancher Server may be unavailable for a few minutes.
**Result:** Your Rancher Servers are upgraded to the latest version.
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 >}}.