drafted HA install procedure, also updated upgrade landing page

This commit is contained in:
Mark Bishop
2018-05-16 18:17:18 -07:00
committed by Mark Bishop
parent c2b78e2461
commit ab45fec416
2 changed files with 41 additions and 6 deletions
+15 -6
View File
@@ -3,14 +3,23 @@ title: Upgrades
weight: 1000
draft: true
---
- Upgrading from Rancher 2.x.x
All Rancher 2.x.x will support upgrades from a previous version. This section will be updated as soon as the first release post 2.0 is available.
This section includes instructions for upgrading Rancher from previous versions.
- Migrating from Rancher 1.6.x
### Upgrading from Rancher 2.x.x
By embarking on the Rancher 2.0 project, all of the legacy Rancher 1.6 Java modules were completely rewritten in Go, and in the process touched just about every other module in the system. As such, there will not be a direct upgrade from 1.6.x to 2.0.
Each new version of Rancher 2.x.x supports upgrades from previous versions of Rancher 2.x.x. This section will be updated as soon as the first release post 2.0 is available.
Our next major milestone will be our 2.1 release that will include a tool that will convert Rancher Compose to Kubernetes YAML. This will help our existing Cattle users from having to start the migration from scratch. However, we know the biggest challenge will be having to leverage Cattle functionality in a Kubernetes environment as you deploy new workloads. We plan to also release a guide that will act as a cheatsheet for those that enjoy Cattle's simplicity and want to quickly create those workloads in Kubernetes.
Complete one of the upgrade procedures below based on your Rancher installation:
We do plan to continue to support Rancher 1.6.x for at least another year after 2.1 has been released to give our users time to plan this migration.
- [Single Node Upgrade](./single-node-upgrade/)
- [High Availability Upgrade](./ha-server-upgrade)
- [Air Gap Upgrade](./air-gap-upgrade)
### Migrating from Rancher 1.6.x
Until Rancher 2.1 is released, migrating to from Rancher 1.6.x to 2.x.x is not supported due to major code rewrites.
For the 2.1 release, we plan to release a tool that converts Rancher Compose to Kubernetes YAML. This tool will help our Cattle users migrate from Rancher 1.6.x to 2.x.x. However, we understand that there is a learning curve switching from Cattle to Kubernetes as you deploy new workloads. Therefore, this release will include a cheatsheet for those that enjoy Cattle's simplicity but want to quickly create those workloads in Kubernetes.
We will continue support for Rancher 1.6.x for a minimum of one year after the 2.1 release so that 1.6.x users can plan and complete migration.
@@ -3,3 +3,29 @@ 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.
1. Log into Rancher and browse to the cluster that your're using to run Rancher.
2. From the cluster dashboard, click **Kubeconfig File**.
**Step Result:** The Kubeconfig file opens in a new window.
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:latest -n cattle-system
```
8. 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 the latest version.