Skip to content

Deletion

Deletion is permanent. Export application data, manifests, and secrets you need before deleting anything. Kupe does not back up in-cluster storage.

In the console, open the cluster, select Delete Cluster, and confirm its name. Or run:

Terminal window
kupe cluster delete prod

The CLI asks for confirmation and waits for deletion. For scripts, use --yes. Deleting a cluster removes its workloads, volumes, and Kupe hostname. It does not delete your databases, registry, managed secrets, or other clusters. Remove custom-domain DNS records you no longer need.

Only the tenant owner can do this. Delete its apps, databases and registry first, disabling deletion protection on the databases and registry when you are ready.

In the console, open Manage Tenant → Danger Zone → Delete Tenant. Confirm the tenant name. This deletes its remaining clusters and their data, managed secrets, dashboards, and access credentials. Members keep their user accounts.

Or, while signed in as the owner with kupe auth login, run:

Terminal window
kupe tenant delete --confirm acme --cascade --wait

--cascade also deletes the tenant’s clusters. Check the active tenant with kupe auth whoami before running the command. An API key cannot delete a tenant.

Leave all tenants first: delete those you own and ask an admin to remove you from the others. Sign in again before deleting your account; your login must be less than 10 minutes old.

After leaving your last tenant, choose Delete my account in the console and confirm your email. Or run:

Terminal window
kupe user delete --confirm you@example.com

Deletion runs in the background. A timeout while waiting does not cancel it. Contact support if deletion appears stuck or you need help with a data-deletion request. See the Privacy Policy for data retention after deletion.

For cluster automation, see Delete a cluster with the API.