Use the Container Service for Kubernetes (ACK) console to delete clusters that are no longer needed. On the deletion page, review the resources to be deleted and select which ones to retain. Read the on-screen notices carefully to ensure you understand the risks before proceeding.
Cluster deletion and node release rules
When you delete a cluster, ACK releases the nodes by sequentially deleting their node pools. The following rules apply to node pools in the cluster:
If a node pool is configured with a desired number of nodes: 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 the nodes in the ECS console. After a node is released, its system disk is also released.
If a node pool is not configured with a desired number of nodes: Subscription nodes and any nodes manually or automatically added to the node pool are not released. All other nodes are released.
For more information, see How do I determine if a node pool has a desired number of nodes configured?
Procedure
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, find the cluster to delete and choose in the Actions column.
In the panel that appears, carefully review the resources that will be automatically deleted, such as ECS, Elastic Container Instance (ECI), and Container Compute Service (ACS) resources. Select any resources you want to retain, read the notes about resource deletion and billing, and then follow the on-screen instructions to delete the cluster.
Clean up resources
After a cluster is deleted, ACK automatically cleans up some of the associated resources. However, certain associated cloud service resources, such as subscription nodes and storage volumes, may not be automatically released with the cluster. After you confirm that the remaining resources are no longer needed, promptly delete them manually to avoid continued charges. Log on to the Resource Management console to view all resources in your account.
The following table lists some of these resources:
Cloud resource | Deletion guide |
ECS nodes (subscription) | First, convert the subscription instances to pay-as-you-go instances (Console/OpenAPI), and then release the instances (Console/OpenAPI). |
VPC | |
vSwitch | |
security group | |
NAT gateway | |
EIP | |
CLB (subscription) | |
NLB | |
ALB | |
Cloud-native API gateway (APIG) | |
MSE Cloud Native Gateway | |
Cloud disk (used as a PV) | |
NAS (used as a PV) | |
OSS bucket (used as a PV) | |
CPFS for AI (used as a PV) | |
CPFS General-purpose (used as a PV) | |
SLS project | |
Prometheus |
FAQ
What if cluster deletion fails?
If the deletion fails, the cluster status changes to delete_failed.
Deletion can fail for the following reasons:
Unexpected resource dependencies
When you delete an ACK cluster, ACK releases the resources selected for deletion and checks their dependencies during the release. For example, if a resource to be deleted has dependencies not created by the cluster, the deletion may fail. Click View in the Cluster Status column to see the cause of the failure. After you resolve the issue, try deleting the cluster again.
For example, if a NAT gateway automatically created by the ACK cluster contains SNAT or DNAT entries not created by the cluster, the deletion may fail.
During the deletion, choose to retain the NAT gateway that failed to be released. After the cluster is deleted, manually release the NAT resources. Alternatively, follow the on-screen instructions to manually remove the blocking SNAT or DNAT entries, and then try to delete the cluster again.
If the cluster deletion fails for other reasons, submit a ticket.
How do I disable cluster deletion protection?
If a cluster has deletion protection enabled, the console prompts you to disable it before the cluster can be deleted. To disable cluster deletion protection:
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Actions page, find the cluster and choose in the Actions column, and then follow the on-screen instructions.
How do I determine if a node pool has a desired number of nodes configured?
-
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 then click the Basic Information tab. In the Scaling Configurations section, check whether a desired number of nodes is configured.
If so, the corresponding number is displayed.
The section also shows the values for Expected Nodes and Actual Nodes.
How are associated cloud product resources billed when my ACK cluster is in a deleting or abnormal state?
All cluster types — Basic Edition, Pro Edition, and ACK dedicated clusters — continue to incur charges for associated resources such as ECS and SLB until those resources are released. This applies to clusters in the following states: Deleting, Delete failed, Inactive, and Unavailable.
For more information, see Cluster lifecycle and Billing overview.
How is an ACK cluster in the Inactive or Unavailable state billed?
You are charged only a cloud resource fee for an ACK managed Basic cluster or ACK dedicated cluster. If an ACK Basic cluster or ACK dedicated cluster is in an abnormal state, the billing of the cloud resources used by the cluster continues.
You are charged a cluster management fee and a cloud resource fee for an ACK managed Pro cluster. When an ACK Pro cluster is in an abnormal state, ACK scales in the control plane of the cluster. After the control plane is scaled in, the billing of cluster management stops but the billing of the cloud resources used by the cluster continues.
For more information, see Cluster lifecycle and Billing rules.
States with no management fees
A cluster management fee is charged only for ACK managed Pro clusters. No cluster management fee is charged for ACK managed clusters or ACK dedicated clusters.
When an ACK managed Pro cluster is in one of the following states, cluster management fees are no longer charged:
-
Initializing
-
Failed
-
Inactive
-
Unavailable
-
Deleting
-
Delete_failed
-
Deleted (The cluster is no longer visible in this state.)
For more information, see Cluster lifecycle and Billing overview.
Why is an associated CLB instance not automatically released after an ACK cluster is deleted?
An associated CLB instance is not automatically released when you delete an ACK cluster. This is because a subscription CLB instance must be converted to a pay-as-you-go instance before it can be released.
Convert the subscription CLB instance to a pay-as-you-go CLB instance (for more information, see CLB Billing FAQ), and then Create and manage CLB instances.
For more information about deleting clusters, see Delete a cluster.