Deleting a Node

If a node is no longer needed, delete it on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl delete node, as this may lead to unexpected results.

Deleting or unsubscribing from a node in a CCE cluster will release the node and services running on the node. Drain the node and back up data before the deletion or unsubscription to prevent services running on the node from being affected.

• Deleting a node will lead to pod migration, which may affect services. Perform this operation during off-peak hours. It is a good practice to drain the node before deletion. For details, see Draining a Node. If pods remain when the node is deleted, CCE will evict them. If a Pod Disruption Budget (PDB) policy is configured for your pods, they may fail to be evicted. In this case, the node will be forcibly deleted after a period of time.
• After a node is deleted, its data will be destroyed. Back up node data beforehand.

• Deleting a node will cause PVC/PV data loss for the local PV associated with the node. These PVCs and PVs cannot be restored or used again. In this scenario, the pod that uses the local PV is evicted from the node. A new pod is created and stays in the pending state. This is because the PVC used by the pod has a node label, due to which the pod cannot be scheduled.

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab.
3. Locate the target node and choose More > Delete in the Operation column.
4. In the Delete Node dialog box, enter DELETE and click Yes.
   Note

   • After the node is deleted, workload pods on the node are automatically migrated to other available nodes.
   • If the disks and EIPs bound to the node are important resources, unbind them first. Otherwise, they will be deleted with the node.