curl --request DELETE \ --url 'https://api.e2enetworks.com/myaccount/api/v1/gpu/tenant_clusters/{tenant_cluster_id}/?project_id=<PROJECT_ID>&location=<LOCATION>&apikey=<API_KEY>' \ --header 'Authorization: Bearer <API_TOKEN>'import requests
response = requests.delete( "https://api.e2enetworks.com/myaccount/api/v1/gpu/tenant_clusters/{tenant_cluster_id}/", params={"project_id": "<PROJECT_ID>", "location": "<LOCATION>", "apikey": "<API_KEY>"}, headers={"Authorization": "Bearer <API_TOKEN>"},)print(response.json())const url = new URL("https://api.e2enetworks.com/myaccount/api/v1/gpu/tenant_clusters/{tenant_cluster_id}/");url.search = new URLSearchParams({ project_id: "<PROJECT_ID>", location: "<LOCATION>", apikey: "<API_KEY>" });
const response = await fetch(url, { method: "DELETE", headers: { "Authorization": "Bearer <API_TOKEN>" },});console.log(await response.json());Deletes the cluster: its control plane, every node pool and node, its storage and the volumes on it, and its kubeconfig. The call returns once the deletion has started, and the cluster shows deleting. A cluster can be deleted in any status except deleting, including failed, which is how a cluster that never came up is cleared.
Reserved IPs attached to the cluster go back to the project’s reserved IPs and stay reserved, and charged, until you release them. A committed pool’s term keeps running and nothing is refunded.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Kubernetes cluster ID, as returned by List Kubernetes Clusters.
Query Parameters
Section titled “Query Parameters”Project ID
Active IAM ID (To access contact person account) Find your Active IAM ID here
Location
Responses
Section titled “Responses”The deletion has started.
object
object
object
Example
{ "code": 200, "data": { "id": 103, "name": "tir-k8s-prod", "project_id": 18773, "region": "Delhi", "status": "queued" }, "errors": {}, "message": "Tenant cluster deletion started successfully"}