> ## Documentation Index > Fetch the complete documentation index at: https://docs.ornn.com/llms.txt > Use this file to discover all available pages before exploring further. # Tear down a cluster > Stops a launch in progress or tears down a cluster. Ornn deletes the cluster's workloads, revokes its access, and sends cleanup to every worker. The cluster stays in state deleting, with teardown stages in progress, while Ornn waits up to five minutes for workers to confirm cleanup; then its record is removed. Workers that never confirm are released anyway and cleaned when they reconnect. Reservation billing continues, and separately provisioned filesystems are not deleted. Repeating the request while the cluster is deleting returns only its state and does not restart cleanup. Teardown is complete when the cluster is absent from listClusters and getClusterAccess returns 404 cluster_not_found; this operation then returns 404 with an empty body. If the state becomes failed instead, send the teardown again, and contact Ornn if it fails twice. Wait for teardown to finish before creating another cluster. See [Tear down the cluster and confirm](/guides/kubernetes-api#7-tear-down-the-cluster-and-confirm) for how to verify completion. CLI equivalent, after `ornn login`: ```bash theme={null} ornn clusters teardown CLUSTER_ID --wait ``` ## OpenAPI ````yaml openapi.yaml POST /v1/orchestrator/controllers/{controller_id}/teardown openapi: 3.1.0 info: title: Ornn compute API version: 1.0.0 description: >- Customer HTTP API for Ornn GPU capacity. It covers reserved capacity and nodes, VM and Bare Metal access, Kubernetes and Slurm clusters, SSH keys, storage volumes and GitHub repositories, private networks, monitoring, buying and selling capacity (Reserve, Market, Spot, and Relist), and billing. API keys are scoped to one organization and act with their creator's access there; account, team, and API-key management stay in the console. Most operations require an approved organization. See https://docs.ornn.com/api-keys to create a key and https://docs.ornn.com/guides/kubernetes-api for an end-to-end Kubernetes integration. Examples use fictional IDs and credentials. The info.version field identifies the contract revision, not a shared API path version. contact: email: support@ornn.com servers: - url: https://api.ornn.com description: Production security: - OrnnApiKey: [] tags: - name: Authentication - name: Reservations - name: GPU nodes - name: Clusters - name: Workers - name: Virtual machines description: >- Choose a VM disk, launch VM access on a reservation, and read each VM's status, launch progress, and SSH connection details. - name: Bare Metal description: >- Launch Bare Metal access on a reservation, read a host's readiness and SSH connection details, and reboot or hard reset it. - name: SSH keys description: >- Register public keys for your organization, choose which keys a VM or Bare Metal reservation uses, and queue key delivery to machines. Slurm clusters take organization key IDs at launch. Kubernetes API access does not use SSH keys. - name: Reserve description: >- Browse reserved-capacity listings and their terms, and post, cancel, or accept offers. Reserve listings are visible to approved organizations. - name: Market description: >- Browse relisted capacity and buy windows at the asking price, paid up front. Open to every member of your organization. - name: Spot description: >- Hourly order books for VMs with 1, 2, 4, or 8 GPUs on one node: read books, trades, and quotes, place and cancel bids, and follow fills. - name: Relist description: >- Sell whole nodes from a reservation you hold at your asking price, and manage those listings. - name: Storage description: >- Managed volumes, their files, and GitHub repository pulls. Volumes belong to the API key's creator in the key's organization. - name: Networks description: >- Organization private networks and the WireGuard configs you use to reach private machines and clusters. - name: Monitoring description: >- Machine telemetry and console logs for capacity your organization holds. Reads are limited to your reservation window. - name: Billing description: >- Invoices, billing summary, usage cost, Ornn credits, and account statements. Saving a card and paying invoices stay in the console. externalDocs: description: REST integration walkthrough url: >- https://docs.ornn.com/guides/kubernetes-access#provision-and-manage-through-rest paths: /v1/orchestrator/controllers/{controller_id}/teardown: post: tags: - Clusters summary: Tear down a cluster description: >- Stops a launch in progress or tears down a cluster. Ornn deletes the cluster's workloads, revokes its access, and sends cleanup to every worker. The cluster stays in state deleting, with teardown stages in progress, while Ornn waits up to five minutes for workers to confirm cleanup; then its record is removed. Workers that never confirm are released anyway and cleaned when they reconnect. Reservation billing continues, and separately provisioned filesystems are not deleted. Repeating the request while the cluster is deleting returns only its state and does not restart cleanup. Teardown is complete when the cluster is absent from listClusters and getClusterAccess returns 404 cluster_not_found; this operation then returns 404 with an empty body. If the state becomes failed instead, send the teardown again, and contact Ornn if it fails twice. Wait for teardown to finish before creating another cluster. operationId: teardownCluster parameters: - name: controller_id in: path required: true description: Cluster id returned by create or list; not a reservation ID. schema: type: string format: uuid example: 44444444-4444-4444-8444-444444444444 responses: '202': description: >- Teardown accepted, or already in progress. Poll for completion. Reservation billing continues. content: application/json: schema: oneOf: - $ref: '#/components/schemas/ClusterAccepted' - type: object required: - state properties: state: type: string additionalProperties: false examples: accepted: summary: First teardown request value: id: 44444444-4444-4444-8444-444444444444 kind: kubernetes organization_id: 22222222-2222-4222-8222-222222222222 access_mode: kubernetes state: deleting network_mode: public endpoint: null credential_state: pending namespace: k8s-22222222-2222-4222-8222-222222222222 node_count: 1 gpu_count: 8 progress: stages: - key: workers label: Release the workers status: running detail: 0 of 1 confirmed - key: namespace label: Delete the cluster namespace status: running detail: null created_at: '2026-10-14T12:00:00Z' updated_at: '2026-10-14T13:00:00Z' repeated: summary: Repeat request while the teardown runs value: state: deleting '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': description: >- The cluster does not exist or is not visible to your organization, including after its teardown finished. This response has no body. default: $ref: '#/components/responses/Error' components: schemas: ClusterAccepted: type: object required: - id - state properties: id: type: string format: uuid kind: type: string organization_id: type: - string - 'null' format: uuid access_mode: type: string state: type: string network_mode: type: string endpoint: type: - string - 'null' credential_state: type: string namespace: type: - string - 'null' description: The namespace Ornn configures for your workloads. node_count: type: integer description: >- Workers attached when this response was built; usually 0 right after a launch. gpu_count: type: integer description: GPUs on the workers counted in node_count. progress: anyOf: - $ref: '#/components/schemas/Progress' - type: 'null' created_at: type: string format: date-time updated_at: type: string format: date-time Progress: type: object description: >- Stages of the latest launch or teardown. Launch stages are create_plane, prepare_hosts, join_workers, apply_plane, and issue_access. Teardown stages include workers and the control-plane stage (namespace for Kubernetes, stack for Slurm), plus nodes or storage when those steps fail. properties: stages: type: array items: type: object properties: key: type: string description: Stable stage identifier. label: type: string description: Display label for the stage. status: type: string enum: - pending - running - completed - failed detail: type: - string - 'null' description: Failure reason or worker confirmation count, when available. Error: type: object properties: code: type: string detail: oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string responses: Unauthorized: description: >- The credential is missing, invalid, revoked, or no longer belongs to a current organization member. Check the HTTP status before parsing the body. content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The credential lacks access to this operation, or the organization requires approval. An API key does not bypass these checks. content: application/json: schema: $ref: '#/components/schemas/Error' Error: description: >- Unsuccessful request. Check HTTP status first. Errors may have detail.code/detail.message, a string detail and optional top-level code, or an empty/non-JSON body. 401: invalid credential; 403: access or approval required; 404: not visible or credentials not ready; 409: lifecycle conflict; 429: back off; 5xx: service failure. Inspect current state before retrying mutations. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: OrnnApiKey: type: http scheme: bearer bearerFormat: ornn_sk_... description: >- Create an organization API key in Account Settings > Developer. Do not send this key to the Kubernetes API server. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.