Skip to main content
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.

Options

Global options

See global options.

SEE ALSO

  • kubox plane - Describe and build a management plane from one document