Cleaning up MSDP Scaleout
When you uninstall the MSDP Scaleout deployment from AKS or EKS, the MSDP engines, MSDP MDS servers, and the data is deleted from the cluster. The data is lost and cannot be recovered.
To clean up MSDP Scaleout from AKS or EKS
- Delete the MSDP Scaleout CR.
kubectl delete -f <sample-cr-yaml>
When an MSDP Scaleout CR is deleted, the critical MSDP data and metadata is not deleted. You must delete it manually. If you delete the CR without cleaning up the data and metadata, you can re-apply the same CR YAML file to restart MSDP Scaleout again by reusing the existing data.
- If your storage class is with the Retain policy, you must write down the PVs that are associated with the CR PVCs for deletion in the Kubernetes cluster level.
kubectl get pod,svc,deploy,rs,ds,pvc,secrets,certificates,issuers,cm,sa,role,rolebinding -n <sample-namespace> -o wide
kubectl get clusterroles,clusterrolebindings,pv -o wide --show-labels|grep <sample-cr-name>
- Delete all resources under the namespace where MSDP CR is deployed.
kubectl delete namespace <namespace>
- If your storage class is with the Retain policy, you must delete the Azure disks using Azure portal or delete the EBS volumes using Amazon console. You can also use the Azure or AWS CLI.
AKS: az disk delete -g $RESOURCE_GROUP --name $AZURE_DISK --yes
EKS: aws ec2 delete-volume --volume-id <value>