OpenFrame Documentation
Deployment guides, the CLI reference, architecture and admin guides for OpenFrame
OpenFrame is on your phone now! · iOS and Android apps are live. Get alerts and handle tickets on the go!
Deployment guides, the CLI reference, architecture and admin guides for OpenFrame
This guide shows the person operating an OpenFrame deployment how to remove the OpenFrame platform from a cluster and, if the cluster itself is no longer needed, delete the cluster entirely.
openframe command runs from your terminal. See How to update the OpenFrame CLI to the latest version if you are not sure which version you have.openframe app uninstall and openframe app upgrade warn you that "a dim line naming the current kube-context" is shown before destructive operations, as "the cheapest guard against installing onto the wrong cluster."openframe cluster list or openframe cluster status [NAME], described in How to check the status of your OpenFrame cluster and app.gcloud for GKE, aws for EKS), since deleting it tears down billed infrastructure.openframe app uninstall to remove OpenFrame but keep the cluster running, or continue to cluster deletion if you want the cluster gone too. The command's own description states: "Deletes the ArgoCD applications and uninstalls the ArgoCD and app-of-apps Helm releases. The cluster itself is NOT deleted."--context flag, for example openframe app uninstall --context k3d-openframe-dev. Do not pass the cluster name as a plain argument — the command rejects positional arguments and tells you to use --context instead, to avoid acting on the wrong cluster.--yes flag (for example openframe app uninstall --yes). Without a terminal to prompt in, the command refuses to run unless --yes is given.--delete-namespace (for example openframe app uninstall --yes --delete-namespace) if you also want the argocd namespace removed after the applications and Helm releases are gone.Uninstalling OpenFrame..., followed by a success line reporting how many applications and Helm releases were removed, and — if you asked for it — a line confirming the argocd namespace was deleted.openframe cluster delete [NAME]. Omitting the name triggers interactive selection; the command prunes Docker resources, deletes the cluster, and removes its configuration.openframe cluster delete with no argument and pick the cluster from the interactive list the command presents.--force (for example openframe cluster delete my-cluster --force). In a non-interactive session without --force, the command refuses outright rather than hang on a prompt or guess an answer.openframe app uninstall succeeds, you see a line such as Removed N application(s) and N Helm release(s)., optionally Deleted the argocd namespace., and finally The cluster was left running. Re-install any time with: openframe app install.Uninstall cancelled. and nothing is removed.openframe cluster delete succeeds, the CLI reports the operation as successful for the named cluster and its detected type (k3d, GKE, or EKS); the cluster, its Docker resources (for k3d), and its configuration entry are gone.Cluster name did not match — nothing was deleted, and the cluster is left untouched."app uninstall" takes no positional arguments (got "...") — use --context to target a cluster: you passed a cluster name directly after uninstall. Re-run the command with --context <name> instead.refusing to destroy cloud cluster '<name>' non-interactively; pass --force to confirm: you ran openframe cluster delete against a GKE or EKS cluster from a non-interactive session (for example a CI job) without --force. Add --force if you are certain, or run the command interactively so you can re-type the cluster name to confirm.Cluster name did not match — nothing was deleted: you were asked to re-type the cloud cluster's name to confirm deletion and what you typed did not match exactly. Run openframe cluster delete <name> again and type the name precisely, or pass --force to skip the prompt.openframe app uninstall is waiting for a yes/no confirmation. Either answer the prompt, or re-run with --yes (for uninstall) or --force (for cloud cluster delete) if you intend to automate it.openframe app uninstall only removes OpenFrame (ArgoCD and its apps, and optionally the argocd namespace); it never deletes the cluster. Use openframe cluster delete separately if you also want the cluster gone.openframe cluster delete has completed; treat the deletion as final.