curl --request DELETE \
--url https://api.qovery.com/organization/{organizationId}/cluster/{clusterId} \
--header 'Authorization: Bearer <token>'curl --request DELETE \
--url https://api.qovery.com/organization/{organizationId}/cluster/{clusterId} \
--header 'Authorization: Bearer <token>'JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '
Organization ID
Cluster ID
Indicates the mode to apply on cluster deletion
"hard delete" means that we delete directly from our database, this is different from a "trigger delete" that cleans the resource
DEFAULT: this is the normal way, trigger delete the cluster only if no environment linked to this cluster remainsDELETE_CLUSTER_AND_QOVERY_CONFIG: hard delete environments linked to this cluster then trigger delete the clusterDELETE_QOVERY_CONFIG: ⚠️ ⚠️ ⚠️ hard delete environments linked to this cluster then hard delete the cluster - whole cluster ressources are not deleted on our side and must be deleted on your sideDEFAULT, DELETE_CLUSTER_AND_QOVERY_CONFIG, DELETE_QOVERY_CONFIG "DEFAULT"
The resource was deleted successfully
Was this page helpful?