RArafftechnologies
Kubernetes

Delete node pool

Changed on

Remove a pool and all its nodes. Each node is cordoned and drained (PodDisruptionBudgets are honoured) before its VM is terminated, one at a time; the operation runs asynchronously and stops — with the pool intact — if a node cannot be emptied.

The last pool of a cluster cannot be deleted, and the cluster keeps at least 2 worker nodes.

delete/api/v1/k8s/clusters/{cluster_id}/pools/{pool_id}

Request

  • Base URL
    https://api.rafftechnologies.com
  • URL
    https://api.rafftechnologies.com/api/v1/k8s/clusters/{cluster_id}/pools/{pool_id}
  • Auth
    API key in header X-API-Key

Path parameters

cluster_idstring required

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

pool_idstring uuid required

Node pool ID

Headers

X-Project-IDstring uuid required

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

Response

Pool deletion started

successboolean
messagestring

Example response

{
  "success": true,
  "message": "Operation completed successfully"
}

Changes