All Products
Search
Document Center

Container Service for Kubernetes:Migrate unmanaged worker nodes to a node pool

Last Updated:Mar 07, 2026

In older ACK clusters created before the node pool feature was released, some worker nodes may not be managed by any node pool. If you no longer need these nodes, release their ECS instances directly. If you want to keep them, add them to a node pool for grouped management and automated operations and maintenance.

Step 1: Create and scale out a node pool

Before migration, create a node pool and scale it out. Set the desired number of nodes to match the number of unmanaged nodes. Configure the node pool with the same specifications as the unmanaged nodes.

  1. Log on to the Container Service Management Console . In the navigation pane on the left, click Clusters.

  2. On the Clusters page, click the name of your cluster. In the navigation pane on the left, click Nodes > Node Pools.

  3. In the upper-right corner of the Node Pools page, click Create Node Pool. Configure the parameters and click Confirm.

    For details about configuration items, see Create and manage node pools.

Step 2: Remove unmanaged nodes

Remove unmanaged nodes from the ACK console. Clear the Release ECS Instance check box. For detailed steps, see Remove nodes.

Step 3: Add existing nodes

After removing the nodes, add their ECS instances back to the node pool. For steps and important notes, see Add existing nodes.

References

  • A managed node pool is an ACK node pool that supports automated operations and maintenance. It provides automatic fault recovery, automatic kubelet upgrades, and automatic CVE fixes. This reduces the operational burden of managing node pools. For more information, see Managed node pool overview.

  • Scale a node pool in or out by setting its desired number of nodes. This keeps the node count at the desired level and helps reduce costs. For more information, see Manually scale node pools.

  • Compare runtimes supported by node pools, such as containerd and Docker. For more information, see Compare containerd, sandboxed containers, and Docker runtimes.

  • To avoid security and stability risks from outdated clusters, upgrade your ACK cluster to the latest version. For detailed steps, see Manually upgrade a cluster.

  • To release ECS instances, see Release an instance.