Migrating the MSDP Scaleout to another node pool

You can migrate an existing MSDP Scaleout on another node pool in case of the Kubernetes infrastructure issues.

To migrate the MSDP Scaleout to another node pool

Ensure that no job running related to MSDP Scaleout that is going to migrate.
Update the node selector value spec.nodeSelector to the new node in the CR YAML file.
Apply new CR YAML to update the CR in the Kubernetes environment.
kubectl apply -f <your-cr-yaml>
Note:
All affected pods or other Kubernetes workload objects must be restarted for the change to take effect.
Delete all the pods and deployments in the namespace of MSDP Scaleout manually.
kubectl get pod,deploy -n <sample-namespace>
kubectl delete -n <sample-namespace> <pod1> <pod2> ... <podn> <deployment>
After you run the commands, the pods are re-scheduled onto the new node pool automatically.
Run the following command to change MSDP Scaleout operator to the new node pool:
kubectl msdp init -i <your-acr-url>/msdp-operator:<version> -s <storage-class-name> -l agentpool=<new-nodepool-name>
If MSDP Scaleout operator pod is not restarted, manually delete the pods in the namespace of MSDP Scaleout operator. After that, the Pods of MSDP Scaleout operator would be re-scheduled onto the new node pool.
kubectl get pod -n msdp-operator-system
kubectl delete -n msdp-operator-system pod <MSDP operator pod>
After you run the commands, the MSDP Scaleout operator pods are re-scheduled onto the new node pool.