Skip to main content
Version: Operator 3.2.2

Delete an Aerospike Cluster on Kubernetes

Be cautious when deleting clusters. Deleting a cluster causes a complete shutdown of all pods (nodes) in the cluster, which may not be recoverable. When a cluster (CR) is deleted, all the resources created by the operator for that cluster are permanently lost.

Whether data in a Persistent Volume Control (PVC) is deleted or retained depends on the cascadeDelete flag set in the CR. Data persistence also depends on the underlying storageClass as well, which is set by the Kubernetes administrator and is not part of the Aerospike Operator.


If you delete the Kubernetes cluster instead of the Aerospike cluster, and you are using a cloud provider like AWS, delete persistent storage volumes as a separate step.

Persistent storage volumes are not automatically deleted when you delete the Kubernetes cluster. This protects your persistent storage data.

However, your cloud provider will continue to charge you for these storage volumes.

If you are using a local solution like Minikube, you can delete the cluster with minikube delete or kubectl delete.

Run kubectl delete on the Custom Resource (CR) file to delete the cluster. For example:

kubectl delete -f aerospike-cluster.yaml