Call the ScaleClusterNodePool operation to scale out a node pool, which adds more nodes to support your workloads. The count parameter must be greater than the current number of nodes in the pool. If a node pool contains failed nodes, first call the DeleteClusterNodes operation to remove them before scaling out the pool. A scale-out operation typically completes in 5 to 10 minutes. If the operation takes longer than one hour, it has failed. Contact technical support.
Operation description
Each user is limited to 10 calls per second.
Scaling out a node pool is an asynchronous operation that typically completes in 5 to 10 minutes.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
ens:ScaleClusterNodePool |
update |
*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. |
np2201da356f5245cf8faa522a8a4c8224 |
| Body |
object |
No |
The request body. |
|
| Count |
integer |
Yes |
The desired instance count. |
0 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response schema. |
||
| RequestId |
string |
The request ID. |
C0003E8B-B930-4F59-ADC0-0E209A9012A8 |
Examples
Success response
JSON format
{
"RequestId": "C0003E8B-B930-4F59-ADC0-0E209A9012A8"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.