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.
- Navigate to the helm directory within the extracted tar location.
- Run the following command to get the Cloud Scale release name:
Helm ls -n <namespace>
- Run the following command to migrate MSDP Scaleout to new node pool:
helm upgrade <release-name> cloudscale-<version>.tgz -n netbackup --reuse-values
--set environment.msdpScaleouts.nodeSelector.labelKey=<new-value>
--set environment.msdpScaleouts.nodeSelector.labelValue=<new-value>
- After the helm upgrade, existing pods are terminated and restarted one at a time, and the pods are re-scheduled for the new node pool automatically.
Note:
Controller pods are temporarily unavailable when the MDS pod restarts. Do not delete pods manually.
- Re run the following command to update the MSDP Scaleout operator with new node pool:
# helm upgrade --install operators
- If node selector does not match any existing nodes at the time of change, you see the message on the console.
If auto scaling for node is enabled, it may resolve automatically as the new nodes are made available to the cluster. If invalid node selector is provided, pods may go in the pending state after the update. In that case, run the command above again.
Do not delete the pods manually.