Migrating the node pool for primary or media servers
You can migrate the node pool for primary or media servers.
To migrate the node pool for primary or media servers
- Edit environment CR object using the <environmentCR_name> -n <namespace> command.
Remove keySecret name and passphrase field from msdpScaleout section in CR object.
Set paused field to true in primary or media section and save.
- Edit primary or media statefulset using the kubectl edit statefulset.apps/<sts-name> -n netbackup-environment command , set replica count to 0 and save.
The pods are deleted.
- Run the kubectl describe statefulset.apps/<sts-name> -n <namespace> command:
Wait till the pod status displays 0 Running. Depending on replica count and server load, time taken to delete the pods may change.
During the node pool migration for the primary server, media server or MSDP Scaleout pods may go into a not ready state (0/1). After the primary server pod goes into a running state, the media server or msdp pods will be in ready state.
- Edit the primary or media statefulset using the following command and update node selector with label key and value for new node pool and save
kubectl edit statefulset.apps/<sts-name> -n <namespace>
- Edit environment CR object, update node selector with the same node selector value and set paused to false.
Pods are created on new node pool with the same persistent storage volumes. All the pods will be in ready and running state.