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 you want to repurpose
To troubleshoot installation issues

The uninstall process removes the following:

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)

Before you begin, verify that you have the following:

Administrative access to your Kubernetes cluster
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.

Helm installation

To uninstall Mission Control, do the following:

Uninstall the Helm release:
```
helm uninstall mission-control -n NAMESPACE
```
Replace NAMESPACE with your namespace. The default namespace is mission-control.
Verify remaining pods in the namespace:
```
kubectl get pods -n NAMESPACE
```
Delete the namespace:
```
kubectl delete namespace NAMESPACE
```
If you deployed global-scoped database clusters (not namespace-scoped clusters), delete the namespaces where you deployed those clusters:
```
kubectl delete namespace CLUSTER_NAMESPACE
```
Replace CLUSTER_NAMESPACE with each namespace containing a global-scoped cluster.

Delete the clusterconfigs.datastax.com CRD:

kubectl delete crd clusterconfigs.datastax.com

If you installed Mission Control using Helm with separate cluster resources, delete the cluster-scoped resources that you applied:
```
kubectl delete -f MISSION_CONTROL_CLUSTER_RESOURCES_FILE.yaml --namespace NAMESPACE
```
Replace the following:
- NAMESPACE: Your namespace
- MISSION_CONTROL_CLUSTER_RESOURCES_FILE.yaml: The filename of your cluster resources file

OpenShift installation

If you installed Mission Control in an OpenShift environment, do the following:

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 you uninstall Mission Control, clean up any remaining resources.

Remove persistent volume claims (PVCs)

Run this command:

kubectl delete pvc --all -n NAMESPACE

Replace 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 NAMESPACE

Replace NAMESPACE with your namespace. The default namespace is mission-control.

Troubleshooting

If you encounter issues, do the following:

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 yes correctly at the force prompt.