Hot migrating a Basic ACK cluster to a Pro ACK cluster
You can hot migrate an ACK basic cluster to an ACK Pro cluster without interrupting services or affecting running workloads. A successful migration cannot be rolled back.
An ACK Pro cluster builds on the ACK basic cluster. It is designed for large-scale enterprise production environments and provides enhanced reliability, security, and a financially backed service level agreement (SLA).
An ACK basic cluster is suitable for personal learning and testing. It has the following limitations: a maximum of 2 clusters per account, a maximum of 10 nodes per cluster, and no guaranteed availability for the control plane. To increase cluster scale and ensure control plane high availability, we recommend migrating to an ACK Pro cluster. For a detailed comparison, see Cluster types.
Precautions
|
Item |
Description |
|
Billing |
Migrating an ACK basic cluster to an ACK Pro cluster incurs additional cluster management fees from ACK. Billing for other cloud resources is not affected. |
|
Kubernetes version |
The Kubernetes version of the cluster remains unchanged after migration. If you need to migrate the cluster and upgrade its Kubernetes version, we recommend that you complete the migration before you upgrade the Kubernetes version. |
Procedure
The migration process includes two stages: a precheck and the cluster migration. The ACK basic cluster must pass the precheck before the migration to an ACK Pro cluster can begin.
If the precheck fails, follow the on-screen instructions to view failure details and resolve the issues.
-
Log on to the ACK console. In the left navigation pane, click Clusters.
-
On the Clusters page, find the ACK basic cluster that you want to migrate. In the Actions column, choose .
-
In the dialog box that appears, review the notes and click Precheck.

After you click Precheck, you are redirected to the Container Intelligent Service (CIS) console. Click Run Migration Check to start the precheck. If the check fails, you can view the details and resolve the issues on the Migration Check page.
-
After the precheck passes, return to the migration dialog box, review the notes, and then click OK.
After the migration is successfully completed, the Cluster Specification of the target ACK basic cluster on the cluster list page will be automatically changed from Basic to Pro.
FAQ
Are workloads in an ACK basic cluster affected during the migration?
During the cluster migration process, the control plane components of the ACK basic cluster are suspended, but this does not affect your running services.
How long does the migration take?
The process takes approximately 10 to 15 minutes, which includes an expected control plane downtime of 5 to 10 minutes.
Does the access endpoint change after migration?
No. The SLB IP address of the API server does not change, and the cluster address in your KubeConfig file remains the same.
Related topics
-
To upgrade the Kubernetes version of your cluster after migration, see Upgrade a cluster.
-
After migrating to an ACK Pro cluster, you must restrict the worker RAM role permissions to enhance node security. For more information, see Manually restrict the permissions of the worker RAM role for an ACK managed cluster.
-
To migrate an ACK dedicated cluster, see Hot migrate an ACK dedicated cluster to an ACK Pro cluster.