Deleting a Cluster

Scenario

You can directly delete pay-per-use clusters. For details, see Deleting a Pay-per-Use Cluster.
Yearly/Monthly clusters cannot be deleted directly. Unsubscribe from clusters that have not expired or release clusters that have expired and have not been renewed. For details, see Unsubscribing from or Releasing a Yearly/Monthly Cluster.

Precautions

Deleting a cluster will not delete the yearly/monthly-billed resources in the cluster, and their billing continues.
Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related data has been backed up or migrated.
If you choose to delete a cluster with the nodes in it, the system disks and data disks attached to the nodes will also be deleted. Back up data before the deletion.
If you delete a cluster that is not running (for example, frozen or unavailable), associated resources, such as storage and networking resources, will remain.

Deleting a Pay-per-Use Cluster

A hibernated cluster cannot be deleted. Wake up the cluster and try again.

Log in to the CCE console. In the navigation pane, choose Clusters.
Locate the cluster to be deleted, click ... to view more operations on the cluster, and choose Delete.

Figure 1 Deleting a cluster

In the displayed Delete Cluster dialog box, select the resources to be released.

When you delete nodes from a cluster, the following options are available:
- Retain: The node as well as the data on the system disk and data disks will be retained.
- Delete: The node will be deleted with the cluster. This option is available only for pay-per-use nodes. To delete a yearly/monthly node, manually unsubscribe from the node.
- Reset: The node will be retained and reset. The data on the system disk and data disks will not be retained.

Delete cloud storage resources associated with workloads in the cluster.

When deleting underlying cloud storage resources bound to storage volumes in a cluster, pay attention to following constraints:

The underlying storage resources are deleted according to the reclamation policy you defined for the storage volumes. For example, if the reclamation policy of storage volumes is Retain, the underlying storage resources will be retained after the cluster is deleted.
If there are more than 1000 files in the OBS bucket, manually clear the files and then delete the cluster.

If the storage volume's reclamation policy is set to Retain, the following table lists the method of deleting PVs based on their type.

PV Type	Associated Underlying Storage	Whether to Delete Underlying Storage
EVS	Disks	Yes
DSS	Disks	Yes
SFS	SFS Capacity-Oriented or SFS 3.0	Yes
OBS	OBS buckets or parallel file systems	Yes
SFS Turbo	SFS Turbo file systems	Yes
Local PV	Logical volumes mounted to the node	Determined based on the policy selected when the cluster is deleted. If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.
SFS 3.0 subdirectory	A directory in SFS 3.0	No
SFS Turbo subdirectory	A directory in SFS Turbo	No

Delete network resources such as load balancers in a cluster. (Only automatically created load balancers will be deleted).
Delete all log groups, including their log streams, for the cluster in LTS.

If you do not select this option, the LTS logs will not be deleted, and you will be billed for them. For details, see Price Calculator.

Enter DELETE and click Yes to start deleting the cluster.

The delete operation takes 1 to 3 minutes to complete.

Unsubscribing from or Releasing a Yearly/Monthly Cluster

When you unsubscribe from or release a cluster, only the resources associated with the order are unsubscribed from. Non-associated resources are retained and their billing keeps going.
For a yearly/monthly cluster, if the retention expires, the cluster will be automatically released. For the nodes in the cluster, if they expire at the same time, they will also be released. If not, CCE will not perform any operation on your nodes. Node data is retained and the billing keeps going. Pay attention to the expired clusters under your account and renew them in a timely manner to prevent data loss caused by node reinstallation.
If an order contains resources in a primary-secondary relationship, unsubscribe from the resources separately.
For details about unsubscription rules, see Unsubscription Rules.
- If you are unsubscribing from a resource that is being used, review the resource information and refund information carefully. The resource cannot be restored after unsubscription. If you want to reserve your resources and unsubscribe from only the unused renewal periods, log in to the Enterprise Projects console and unsubscribe from renewal period as prompted.
- Unsubscribing from a resource associated with other yearly/monthly-billed resources may affect the normal use of those resources.
  Unsubscribing from a resource associated with other pay-per-use resources will not affect the normal use of those resources. They will be billed normally.
- If your operation is not a five-day unconditional unsubscription, you will be charged for the handling fee and the used amount. Used cash coupons and discount coupons will not be refunded.

Log in to the CCE console. In the navigation pane, choose Clusters.
Locate the cluster to be unsubscribed from, click ... to view more operations on the cluster, and choose Unsubscribe or Release.

Figure 2 Unsubscribing from a cluster

On the displayed page, select the resources to be released.

When you delete nodes from a cluster, the following options are available:
- Retain: The node as well as the data on the system disk and data disks will be retained.
- Delete: The node will be deleted with the cluster. This option is available only for pay-per-use nodes. To delete a yearly/monthly node, manually unsubscribe from the node.
- Reset: The node will be retained and reset. The data on the system disk and data disks will not be retained.

Delete cloud storage resources associated with workloads in the cluster.

When deleting underlying cloud storage resources bound to storage volumes in a cluster, pay attention to following constraints:

The underlying storage resources are deleted according to the reclamation policy you defined for the storage volumes. For example, if the reclamation policy of storage volumes is Retain, the underlying storage resources will be retained after the cluster is deleted.
If there are more than 1000 files in the OBS bucket, manually clear the files and then delete the cluster.

If the storage volume's reclamation policy is set to Retain, the following table lists the method of deleting PVs based on their type.

PV Type	Associated Underlying Storage	Whether to Delete Underlying Storage
EVS	Disks	Yes
DSS	Disks	Yes
SFS	SFS Capacity-Oriented or SFS 3.0	Yes
OBS	OBS buckets or parallel file systems	Yes
SFS Turbo	SFS Turbo file systems	Yes
Local PV	Logical volumes mounted to the node	Determined based on the policy selected when the cluster is deleted. If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.
SFS 3.0 subdirectory	A directory in SFS 3.0	No
SFS Turbo subdirectory	A directory in SFS Turbo	No

Delete network resources such as load balancers in a cluster. (Only automatically created load balancers will be deleted).
Delete all log groups, including their log streams, for the cluster in LTS.

If you do not select this option, the LTS logs will not be deleted, and you will be billed for them. For details, see Price Calculator.