Terminating a DataStax Enterprise Cluster
DataStax Mission Control is current in Private Preview. It is subject to the beta agreement executed between you and DataStax. 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 contact your DataStax account team.
The DataStax Mission Control operators manage or reconcile DSEClusters. Terminating a DataStax Enterprise (DSE) cluster is a straightforward and simple task.
Kubeconfig file` or
contextpointing to a
Control PlaneKubernetes cluster.
Terminate a DSECluster with the
kubectl delete command. One simple command deletes the associated
DSECluster and then various operators automatically handle cleanup of resources.
All underlying objects that are created on behalf of the DSECluster are also deleted. This includes objects in
Data Plane clusters.
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
Terminate with a DSECluster 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 DSECluster is deleted, use a