> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kubox.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# kubox plane delete

Delete the management plane, and nothing it manages

### Synopsis

Destroys the plane's own cluster -- its nodes, its Kubernetes, the Kubox
workloads and the network they sit in -- through the same primitive
`kubox admin delete` uses, against the custody the plan names.

And NOTHING ELSE. The identity plane, the DNS zone, the state backend, the
two keys and the record store survive, and so does every managed cluster:
they continue running, unmanaged, until a plane exists again.

The registrations do not survive on their own. Every CloudAccount, the
External ID its customer's role trusts, every cluster record and every
agent credential live in the plane's store, so they are EXPORTED before it
is destroyed, to a file `kubox plane create --restore-registrations` writes
back into the next plane before its operator starts. An export that fails
stops the delete; nothing is destroyed.

The identity plane cannot be reached by this command by construction: the
only classification it has is existing/retain, and the apply destroys only
what is classified for deletion.

Asks before acting unless --yes.

```
kubox plane delete [flags]
```

### Options

```
      --artifact-key-provider string   key sealed artifacts are protected by (env: KUBOX_ARTIFACT_KEY_PROVIDER)
      --context string                 context within it
      --export-to string               where to write the registrations before the plane is destroyed (default: <name>.registrations.yaml beside the deployment)
  -f, --file string                    the PlaneDeployment being deleted
  -h, --help                           help for delete
      --kubeconfig string              the plane being deleted; its registrations are exported before it is destroyed
      --namespace string               namespace the plane is installed in (default "kubox-system")
      --plan                           say what would be deleted and preserved, and do nothing
      --plane-document string          the document the plane's own cluster was built from; refused unless it names that cluster (default: <name>.cluster.yaml beside the deployment, written if absent)
      --stack-key-provider string      key Pulumi state is encrypted with; must be a DIFFERENT key (env: KUBOX_STACK_KEY_PROVIDER)
      --state-backend string           Pulumi state backend (env: PULUMI_BACKEND_URL)
      --yes                            do not ask for confirmation
```

### Global options

See [global options](/cli-reference/kubox#global-options).

### SEE ALSO

* [kubox plane](/cli-reference/kubox_plane)	 - Describe and build a management plane from one document