Skip to main content
POST
Scale node pool
Updated August 24, 2026
Scaling runs asynchronously. Scale-down drains the newest nodes first, honouring PodDisruptionBudgets — a node that cannot be emptied within 10 minutes stops the operation with the reason in the pool’s status_message. Scale-up on subscription-billed clusters goes through the dashboard checkout (409 here).

Authorizations

X-API-Key
string
header
required

API key for authentication. Each key is bound to a specific account.

Headers

X-Project-ID
string<uuid>
required

Project ID. Required for all mutating operations (create, delete, power actions, resize).

Path Parameters

cluster_id
string
required

Cluster ID (short id, e.g. q7z7zg)

pool_id
string<uuid>
required

Node pool ID

Body

application/json
node_count
integer
required
Required range: 2 <= x <= 20
Example:

3

Response

Scaling started

success
boolean
message
string
new_node_count
integer
Last modified on August 24, 2026