You can delete unneeded clusters in the ACK console. The deletion page lists the resources in the cluster. You can review the resources scheduled for deletion and choose which to retain. Deleting a cluster is irreversible. Read the on-screen instructions carefully to understand the risks before you proceed.
Cluster deletion and node release
When you delete a cluster, ACK sequentially deletes the node pools to release the nodes. The release behavior for nodes in a node pool is as follows:
For a node pool with the expected number of nodes enabled: All pay-as-you-go nodes in the node pool are released. Subscription nodes are not released. To release subscription nodes, log on to the ECS console, convert the subscription nodes to pay-as-you-go nodes, and then release them in the ECS console. When a node is released, its system disk is also released.
For a node pool without an expected number of nodes configured: Manually or automatically added nodes and all subscription nodes are not released. All other nodes are released.
For more information, see How do I check if a node pool has the expected number of nodes enabled?.
Procedure
Step 1: Disconnect the external cluster (optional)
Console
Log on to the ACK console. In the left navigation pane, click Clusters.
-
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
On the Deployments page, switch the Namespace to kube-system, find the ack-cluster-agent deployment, and then click in the Actions column.
CLI
Run the following command on the external cluster to disconnect it from the registered cluster.
kubectl delete deploy ack-cluster-agent -n kube-system Step 2: Delete the registered cluster
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to delete and choose in the Clusters column.
In the Delete Cluster panel, carefully review the resources that will be automatically deleted, such as ECS instances and Elastic Container Instances (ECI). Select any resources that you want to retain. Read the notes about resource deletion and billing, and then follow the on-screen instructions to complete the deletion.
FAQ
Troubleshoot cluster deletion failures
If a cluster deletion fails, its status changes to delete_failed, as shown in the following figure.
A deletion failure may occur for the following reasons:
Resource dependency issues
When you delete an ACK cluster, ACK attempts to release the resources that you selected for deletion and checks for dependencies during the process. For example, if a resource scheduled for deletion has an external dependency (a dependency not created by the cluster), the deletion might fail. In the Cluster Status column, click View to check the failure reason. After you resolve the issue, try deleting the cluster again.
For example, if the NAT Gateway automatically created by the ACK cluster contains SNAT or DNAT entries that were not created by the cluster, the deletion may fail, as shown in the following figure.
You can choose to retain the NAT Gateway that failed to release and then manually manage the resource after the cluster is deleted. Alternatively, you can follow the on-screen instructions to manually resolve the SNAT or DNAT entries that are blocking the deletion, and then try deleting the cluster again.
If the cluster fails to delete due to other reasons, submit a ticket.
How do I disable cluster deletion protection?
If a cluster has deletion protection enabled, you must disable it before deleting the cluster. To disable cluster deletion protection, follow these steps:
Log on to the ACK console. In the left navigation pane, click Clusters.
In the Actions column of the cluster, choose and follow the on-screen instructions.
Check the number of expected nodes
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
Click the name of the target node pool and click the Basic Information tab. In the Scaling Configurations section, check if the expected number of nodes is enabled.
If it is enabled, the number of nodes is displayed.
Billing during cluster deletion or failure
When a cluster is in the deleting or delete_failed state, no cluster or node management fees are charged. However, you are still charged for associated cloud product resources. For more information about the cluster lifecycle, see cluster lifecycle. For billing details of registered clusters, see Billing of cloud resources for registered clusters.
Billing for inactive or unavailable clusters
When a cluster is in an inactive or unavailable state, you are still charged for cluster management and associated cloud product resources. For detailed billing information, see Billing of cloud resources for registered clusters.
Lifecycle states without management fees
A cluster does not incur management fees when it is in the initial, failed, deleting, delete_failed, or deleted state. The deleted state is not visible to users. However, you are still charged for associated cloud product resources. For more information about the cluster lifecycle, see cluster lifecycle. For billing details of registered clusters, see Billing of cloud resources for registered clusters.