Container Service for Kubernetes:Hot migration from ACK dedicated clusters to ACK Pro clusters

1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, choose More > Migrate to Pro in the Actions column of the ACK cluster to be migrated.

3. In the Migrate to Pro dialog box, complete the precheck and Resource Access Management (RAM) authorization, select the OSS bucket that you created for hot migration, and then click OK.

   View how to complete the precheck

   Click precheck to log on to the Container Intelligence Service console. Click Start on the Migration Check page. Then, confirm the check items in the panel that appears, select I know and agree, and then click Start.

   If the cluster fails to pass the precheck, follow the instructions on the page to fix the issues.

   

   View how to complete the RAM authorization

   1. Click RAM console and complete the RAM authorization. Obtain the name of the OSS bucket, which will be used in the following steps.

   2. Click a policy whose name starts with k8sMasterRolePolicy. On the Policy Document tab of the policy details page, click Modify Policy Document. Then, add the following content to the Statement field in the JSON editor and click OK.

      Replace <YOUR_BUCKET_NAME> with the name of the OSS bucket that is specified in the Migrate to Pro dialog box. You need to delete the angle brackets (<>).

      ,
              {
                  "Action": [
                      "oss:PutObject",
                      "oss:GetObject"
                  ],
                  "Effect": "Allow",
                  "Resource": [
                      "acs:oss:*:*:<YOUR_BUCKET_NAME>/*"  
                  ]
              }

   After the migration is complete, the Migrate to Pro dialog box displays a message. You can check the type of the ACK cluster and the status of the master nodes.

   • Cluster type: Go back to the Clusters page. The cluster type in the Type column changes from ACK Dedicated to ACK Pro.

   • Master node status: On the Clusters page, click Details in the Actions column of the cluster. In the left-side navigation pane, choose Nodes > Nodes. If the Role/Status column of the master nodes displays Unknown, the master nodes are disconnected from the cluster. You can refer to Step 2: Remove master nodes from the ACK dedicated cluster after the hot migration is complete to remove master nodes after the hot migration is complete.

Reinstall the ALB Ingress controller

If your ACK dedicated cluster has the ALB Ingress controller installed, you must reinstall it after the migration is complete. For more information about how to install the ALB Ingress controller, see Manage components. After the ALB Ingress controller is installed, you need to use kubectl to run the following command to delete the original Deployment. Before you run the commands, make sure that the kubectl client is connected to the cluster. For more information, see Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster.

kubectl delete deployment alb-ingress-controller -n kube-system

Reinstall the ACK Virtual Node component

If your ACK dedicated cluster has the ACK Virtual Node component installed, to migrate without business interruptions, you must reinstall the ACK Virtual Node component in the ACK Pro cluster after the migration is complete.

1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose Operations > Add-ons.

3. On the Add-ons page, find and install the ACK Virtual Node component.

4. After the ACK Virtual Node component is installed, run the following commands in sequence to delete the original components and configurations.

   # Delete the original vk-webhook Service, ack-virtual-node-controller Deployment, ClusterRoleBindings related to virtual nodes, and virtual node ServiceAccounts in sequence. 
   kubectl -n kube-system delete service vk-webhook
   kubectl -n kube-system delete deployment ack-virtual-node-controller
   kubectl -n kube-system delete clusterrolebinding virtual-kubelet
   kubectl -n kube-system delete serviceaccount virtual-kubelet

5. After the migration is complete, create pods to check whether the cluster runs as normal.