Uninstall Mission Control
This guide explains how to uninstall Mission Control. You might need to uninstall Mission Control for several reasons:
-
To perform a clean reinstallation
-
To migrate to a different version or deployment method
-
To decommission a test or development environment
-
To remove Mission Control from nodes that are being repurposed
-
To troubleshoot installation issues
The uninstall process removes:
-
All Mission Control components and services
-
Configuration files and settings
-
Deployed workloads and their associated resources
-
Database content and stored data
-
Custom resource definitions (CRDs)
The method you use to uninstall Mission Control depends on how you installed it.
Before you begin
Verify that you have:
-
Administrative access to your Kubernetes cluster
-
Access to the KOTS admin interface
-
A backup of any data you want to keep
|
Back up your data before uninstalling. The uninstall process permanently deletes all Mission Control data and configurations. |
Uninstall methods
Choose the method to uninstall Mission Control that matches your installation type.
KOTS installation
If you installed Mission Control using KOTS, run this command:
kubectl kots remove mission-control -n NAMESPACE --undeployReplace NAMESPACE with your namespace.
The default namespace is mission-control.
After uninstalling, remove the KOTS admin ClusterRoles:
kubectl delete clusterrole kotsadm-role
kubectl delete clusterrolebinding kotsadm-rolebindingRuntime installation
If you installed Mission Control using the runtime installer, choose one of these methods:
-
Single-node uninstall
-
Multi-node uninstall
-
Run this command:
sudo ./mission-control reset -
Type
yeswhen prompted to force reset.
Always uninstall non-management nodes first to ensure proper cleanup of worker components.
|
You must run the uninstall command on every node in your cluster to prevent orphaned components. |
Follow these steps to uninstall Mission Control from all nodes:
-
Run the following command on each non-management node:
sudo ./mission-control reset -
Type
yeswhen prompted to force reset. -
After completing all non-management nodes, run the same command on each management node:
sudo ./mission-control reset -
Type
yeswhen prompted to force reset.
Helm installation
If you installed Mission Control using Helm, run this command:
helm uninstall mission-control -n NAMESPACEReplace NAMESPACE with your namespace.
The default namespace is mission-control.
OpenShift installation
If you installed Mission Control in an OpenShift environment:
-
Remove the SCC permissions:
oc adm policy remove-scc-from-user nonroot-v2 -z loki oc adm policy remove-scc-from-user nonroot-v2 -z mission-control oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-agent oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-aggregator oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-cass-operator oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-dex oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-k8ssandra-operator oc adm policy remove-scc-from-user nonroot-v2 -z mission-control-kube-state-metrics -
Uninstall Mission Control.
Clean up remaining resources
After uninstalling Mission Control, clean up any remaining resources.
Remove persistent volume claims (PVCs)
Run this command:
kubectl delete pvc --all -n NAMESPACEReplace NAMESPACE with your namespace.
The default namespace is mission-control.
Delete the namespace
This step is optional. If you don’t plan to reinstall Mission Control, run this command:
kubectl delete namespace NAMESPACEReplace NAMESPACE with your namespace.
The default namespace is mission-control.
Troubleshooting
If you encounter issues:
-
Review the KOTS admin interface logs for error messages.
-
Verify that you have the required permissions.
-
Check that all Mission Control components are healthy before uninstalling.
-
For reset command issues:
-
Verify that you’re using
sudo. -
Confirm that you’re in the correct directory.
-
Check that you typed
yescorrectly at the force prompt.
-
