public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-15 17:43:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

remove 1.6 to 2.0 section

Browse Source
This commit is contained in:
Jason Greathouse
2018-10-02 17:20:06 -05:00
parent 076497bcbe
commit 2e24da61e9
1 changed files with 1 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/upgrades/_index.md
+1 -11
View File
@@ -5,7 +5,7 @@ aliases:
- /rancher/v2.x/en/backups/rollbacks/
---
### Upgrading Rancher 2.x
### Upgrading Rancher
- [Upgrades]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/)
@@ -15,13 +15,3 @@ In the event that your Rancher Server does not upgrade successfully, you can rol
- [Single-Node Rollbacks]({{< baseurl >}}/rancher/v2.x/en/upgrades/single-node-rollbacks)
- [High-Availability Rollbacks]({{< baseurl >}}/rancher/v2.x/en/upgrades/ha-server-rollbacks)
### Migrating from Rancher 1.6.x
Since the underlying orchestration engine in Rancher is now Kubernetes, moving from 1.6 to 2.x is a migration process.
In general, we recommend creating a 2.x instance in parallel with your 1.6 instance. Launch new Kubernetes clusters for your workloads and migrate your workloads when they are ready. When all workloads are migrated, retire the 1.6 instance and clusters.
See our [From Cattle to K8s](https://rancher.com/tags/cattle-to-k8s/) series of articles for tools and information to help you update your workloads to run on Rancher 2.x and 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.