You can call the DeleteClusterNodePool operation to delete a node pool that you no longer need. When you delete a node pool, all pods on its nodes are also deleted. This action may trigger descheduling. If the pods cannot be rescheduled, your services may be affected. Before you delete the node pool, ensure that the cluster has sufficient resources for rescheduling.
Operation description
-
Each user is limited to 10 calls per second.
-
Cluster creation is an asynchronous operation. After the API call is successful, wait 10 to 20 minutes for the cluster to initialize. During this time, you can call the DescribeClustersV1 operation to check the cluster status. After the cluster is created, you can call the DescribeClusterUserKubeconfig operation to obtain the cluster's kubeconfig file.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
ens:DeleteClusterNodePool |
delete |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ClusterId |
string |
Yes |
The ID of the cluster. |
eck-xxxxxxxx |
| NodepoolId |
string |
Yes |
The ID of the node pool. |
np68mi5y1dd748ky37ojo2kqdrz |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
Response schema |
||
| RequestId |
string |
The ID of the request. |
F3B261DD-3858-4D3C-877D-303ADF374600 |
Examples
Success response
JSON format
{
"RequestId": "F3B261DD-3858-4D3C-877D-303ADF374600"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.