Example Analysis of Rancher 2.4.x Migration Custom k8s Cluster

This article is about Rancher 2.4.x migration custom k8s cluster example analysis, the editor feels very practical, so share with you to learn, I hope you can get something after reading this article, say no more, follow the editor to have a look.

I. points for attention

Before doing anything, check that the time of the nodes in all Rancher environments (source Rancher environment and target Rancher environment) is synchronized (important).

For environments where the Rancher is lower than v2.3.x and the custom K8s cluster version is lower than v1.16, due to the change of the K8S cluster API version, the API version mismatch and other permission issues will be prompted after migration. Before migrating, you need to upgrade the source Rancher environment and target Rancher environment to v2.4.x, and upgrade the custom k8s cluster to v1.16 or later before migrating.

Degraded migration is not supported.

After the cluster is imported into the target Rancher environment, the source Rancher environment is retained so that the cluster can roll back until it is confirmed that the cluster migration is completely normal.

II. Basic configuration (optional)

For the source Rancher environment where docker run runs in a single container, it is recommended to execute the following command in the source Rancher container to install the text editing tool vim and configure automatic completion. This step can be ignored in offline environment.

Sed-I's vim bash-com* jqecho. Com source mirrors.ustc.edu.cn source / etc/apt/sources.listapt update & & apt install-y vim bash-com* jqecho 'source