Help Center/ Cloud Container Engine_Autopilot/ FAQs/ Cluster Management/ How Do I Clear Residual Resources After Deleting a Frozen or Unavailable Cluster?
Updated on 2025-09-02 GMT+08:00

How Do I Clear Residual Resources After Deleting a Frozen or Unavailable Cluster?

If a cluster is not in the running state (for example, frozen or unavailable), its resources such as PVCs, Services, and Ingresses cannot be obtained. After the cluster is deleted, there may be residual network and storage resources. In this case, you must manually delete these resources on their respective service console.

Deleting Residual ELB Resources

  1. Go to the ELB console.
  2. Search for load balancers in the VPC by VPC ID used in the cluster.

    Figure 1 Searching for load balancers

  3. In the Listener (Frontend Protocol/Port) column, click the name of the listener to view its details. If the description contains information such as the cluster ID and Service ID, the listener is created for this cluster.

    Figure 2 Listener details

  4. Delete the residual load balancer and related resources from the cluster.

Deleting Residual EVS Resources

An EVS disk dynamically created for a PVC is named in the format of pvc-{UID}. The metadata field in the API contains the cluster ID. You can use this cluster ID to query the EVS disks automatically created for the cluster and delete them as required.

  1. Go to the EVS console.
  2. Use pvc-{UID} to query all EVS disks automatically created for the cluster.

    Figure 3 Searching for EVS disks

  3. Press F12 to open the developer tools. Check whether the metadata field in the detail API contains the cluster ID. If the field contains the cluster ID, the EVS disks are automatically created for the cluster.

    Figure 4 Querying the cluster ID

  4. Delete the residual EVS disks from the cluster.

    Deleted resources cannot be recovered.