Migrating from v1.6 to v2.x
Rancher v2.x has been rearchitected and rewritten with the goal of providing a complete management solution for Kubernetes and Docker. Due to these extensive changes, there is no direct upgrade path from v1.6 to v2.x, but rather a migration of your v1.6 services into v2.x as Kubernetes workloads. In v1.6, the most common orchestration used was Rancher's own engine called Cattle. The following guide explains and educates our Cattle users on running workloads in a Kubernetes environment.
Video
This video demonstrates a complete walk through of migration from Rancher v1.6 to v2.x.
Migration Plan
Want to more about Kubernetes before getting started? Read our Kubernetes Introduction.
Already a Kubernetes user in v1.6?
Get Started is the only section you need to review for migration to v2.x. You can skip everything else.
Migration Example Files
Throughout this migration guide, we will reference several example services from Rancher v1.6 that we're migrating to v2.x. These services are:
- A service named
web, which runs Let's Chat, a self-hosted chat for small teams. - A service named
database, which runs Mongo DB, an open source document database. - A service named
webLB, which runs HAProxy, an open source load balancer used in Rancher v1.6.
During migration, we'll export these services from Rancher v1.6. The export generates a unique directory for each Rancher v1.6 environment and stack, and two files are output into each stack's directory:
docker-compose.ymlA file that contains standard Docker directives for each service in your stack. We'll be converting these files to Kubernetes manifests that can be read by Rancher v2.x.
rancher-compose.ymlA file for Rancher-specific functionality such as health checks and load balancers. These files cannot be read by Rancher v2.x, so don't worry about their contents—we're discarding them and recreating them using the v2.x UI.