Terminate a DataStax Enterprise Cluster

DataStax Mission Control is currently in Public Preview. DataStax Mission Control is not intended for production use, has not been certified for production workloads, and might contain bugs and other functional issues. There is no guarantee that DataStax Mission Control will ever become generally available. DataStax Mission Control is provided on an “AS IS” basis, without warranty or indemnity of any kind.

If you are interested in trying out DataStax Mission Control please join the Public Preview.

The DataStax Mission Control operators manage or reconcile DataStax Enterprise (DSE) clusters. Terminating a DSE cluster is a straightforward and simple task.

Prerequisites

The kubectl CLI tool.
Kubeconfig file or context pointing to a Control Plane Kubernetes cluster.

Procedure

Terminate a DSE cluster with the kubectl delete missioncontrolcluster cluster-name command. This command deletes the associated MissionControlCluster object and DataStax Mission Control automatically handle cleanup of associated resources across Data Planes.

In the case where multiple data plane clusters have DSE nodes that cannot communicate with each other, the deletion operation continues. However, in the case where the Control Plane is not communicating with the Data Plane, DataStax Mission Control is not able to communicate with the Kubernetes API server in the Data Plane cluster, and the deletion operation is halted.

Terminate with a MissionControlCluster Custom Resource

kubectl delete -f my-cluster.dsecluster.yaml

Terminate with a Given Cluster Name

kubectl delete dsecluster my-cluster

To retain the Persistent Volume (PV) after the MissionControlCluster is deleted, use a StorageClass whose reclaimPolicy is set to Retain.