From 2e24da61e94f55f4fbbabb4e7a330155b766934b Mon Sep 17 00:00:00 2001 From: Jason Greathouse Date: Tue, 2 Oct 2018 17:20:06 -0500 Subject: [PATCH] remove 1.6 to 2.0 section --- content/rancher/v2.x/en/upgrades/_index.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/content/rancher/v2.x/en/upgrades/_index.md b/content/rancher/v2.x/en/upgrades/_index.md index 7cb4d024e35..11a78a39648 100644 --- a/content/rancher/v2.x/en/upgrades/_index.md +++ b/content/rancher/v2.x/en/upgrades/_index.md @@ -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. \ No newline at end of file