Upgrading Cloud Scale deployment using Superchart

1. Deactivate all policy and suspend the scheduling.
2. Run the following command and check the operators release version:

   helm ls -n netbackup-operator-system

3. Upload images for operators and Cloud Scale services to a public or private registry.
4. Upgrade operators by specifying the new tags.

   Run the helm command from the following location:

   /VRTSk8s-netbackup-<version>/helm/

   Extract the operators-values.yaml file from the Helm package, make modifications, and upgrade the operators.

   Run the following command with --reuse-values option for upgrading the operators:

   helm upgrade operators operators-<version>.tgz -n netbackup-operator-system --reuse-values

   --set msdp-operator.image.tag=<msdp image tag>

   --set nb-operator.image.tag=<primary image tag>

   --set nb-operator.msdp-operator.image.tag=<msdp image tag>

   --set nb-operator.flexsnap-operator.image.tag=<nbsm image tag>

   --set flexsnap-operator.image.tag=<NBSM image tag>

5. Use the following command to verify the operator pod status:

   kubectl get all -n netbackup-operator-system

6. Depending on the environment, execute the following steps to upgrade the Cloud Scale deployment (fluentbit, postgresql and the environment):

   For non-DBaaS environment: If the service image tag exists in version 11.1, perform the following steps for the PrimaryServer pods.

   • Run the following command:

     helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.paused=true

   • Remove the serviceImagetag section by using the kubectl edit command.

   • Run the following command:

     helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.tag=new-tag --set environment.primary.paused=false

   For example:

    helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values \
                   --set fluentbit.image.tag=<primary image tag> --set fluentbit.cleanup.image.tag=<primary image tag>  \
                   --set postgresql.image.tag=<postgres image tag> --set postgresql.postgresqlUpgrade.image.tag=<postgres image tag> \
                   --set environment.primary.tag=<primary image tag>  \
                   --set environment.mediaServers[0].name=media1 \
                   --set environment.mediaServers[0].replicas=1 \
                   --set environment.mediaServers[0].nodeSelector.labelKey=agentpool  \
                   --set environment.mediaServers[0].nodeSelector.labelValue=mediapool  \
                   --set environment.mediaServers[0].storage.data.capacity=50Gi \
                   --set environment.mediaServers[0].storage.data.storageClassName=managed-csi-hdd \
                   --set environment.mediaServers[0].storage.log.capacity=30Gi  \
                   --set environment.mediaServers[0].storage.log.storageClassName=managed-csi-hdd  \
                   --set environment.mediaServers[0].tag=<primary image tag>  \
                   --set environment.msdpScaleouts.tag=<MSDP image tag> \ 
                   --set environment.cpServer.tag=<NBSM image tag>

   For DBaaS environment: If the service image tag exists in version 11.1, perform the following steps for the PrimaryServer pods.

   • Run the following command:

     helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.paused=true

   • Remove the serviceImagetag section by using the kubectl edit command.

   • Run the following command:

     helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.tag=new-tag --set environment.primary.paused=false

   For example:

   helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values  \
                   --set fluentbit.image.tag=<primary image tag> --set fluentbit.cleanup.image.tag=<primary image tag>  \
                   --set environment.primary.tag=<primary image tag>  \
                   --set environment.mediaServers[0].name=media1 \
                   --set environment.mediaServers[0].replicas=1 \
                   --set environment.mediaServers[0].nodeSelector.labelKey=agentpool  \
                   --set environment.mediaServers[0].nodeSelector.labelValue=mediapool  \
                   --set environment.mediaServers[0].storage.data.capacity=50Gi \
                   --set environment.mediaServers[0].storage.data.storageClassName=managed-csi-hdd \
                   --set environment.mediaServers[0].storage.log.capacity=30Gi  \
                   --set environment.mediaServers[0].storage.log.storageClassName=managed-csi-hdd  \
                   --set environment.mediaServers[0].tag=<primary image tag>  \
                   --set environment.msdpScaleouts.tag=<MSDP image tag>r \ 
                   --set environment.cpServer.tag=<NBSM image tag>

7. Wait for the Environment CR to reach the Ready status. During this period, pods may restart and new services may start.

   kubectl get environment -n namespace

8. Log into the primary server using the kubectl exec -it pod/,primary-podname> -n netbackup -- bash command and resume the backup job processing by using the following command:

   nbpemreq -resume_scheduling