Resize Auto Scaling Group (Cardinality)
Manually sets the number of running nodes (cardinality) for the group. The requested cardinality must be within the group's [min_nodes, max_nodes] range. Set update_min_nodes: true to also raise min_nodes to the new cardinality so autoscaling does not immediately scale back down. A resize is rejected with 412 Precondition Failed if the group is not in a resizable state (for example while it is already SCALING).
/api/v1/scaler/scalegroups/{scaler_id}Path parameters
scaler_idPathintegerrequiredThe
idof the auto scaling group, as returned by List.- required
- must be a valid auto scaling group ID
example12345
Query parameters
project_idQueryintegerrequiredIdentifier of the project to scope the request to. Required integer project ID.
- required
- must be a valid integer project ID
example{{project_id}}apikeyQuerystringrequiredAPI key used to authenticate the request.
- required
- non-empty string
example{{api_key}}locationQuerystringrequiredRegion of the group.
- required
- must be a valid region name (e.g., Delhi, Chennai)
example{{location}}
Request body
application/json
Manually set the number of running nodes for the group.
Target number of running nodes.
2- required
- must be between the group's min_nodes and max_nodes
When true, also raise min_nodes to the new cardinality so autoscaling does not scale back down.
true- optional
- defaults to false
Responses
200Successful response
Resize confirmation. A resize on a group that is not in a resizable state returns 412 Precondition Failed with the reason in errors (for example "Service cannot be scaled in state: SCALING").
200Success