NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

To prepare the images to apply patches

1. Unpack the tar file on a system where docker is able to push to the container registry, and kubectl can access the cluster.
2. Decide on a unique tag value to use for MSDP Scaleout images. For example, 16.0.1-update1. Set the DD_TAG environment variable accordingly and run deploy.sh:

   DD_TAG=16.0.1-update1 ./deploy.sh

3. In the menu that appears, select option 1 to install the operators.
4. Enter the fully qualified domain name of the container registry.

   For example: exampleacr.azurecr.io.

   When the script prompts to load images, answer yes.

5. When the script prompts to tag and push images, wait. Open another terminal window and re-tag the MSDP Scaleout images as:

   docker tag msdp-operator:16.0.1 msdp-operator:16.0.1-update1

   docker tag uss-controller:16.0.1 uss-controller:16.0.1-update1

   docker tag uss-engine:16.0.1 uss-engine:16.0.1-update1

   docker tag uss-mds:16.0.1 uss-mds:16.0.1-update1

6. Return to the deploy script and when prompted, enter yes to tag and push the images. Wait for the images to be pushed, and then the script will pause to ask another question. The remaining questions are not required, so press Ctrl+c to exit the deploy script.

1. Get the image ID of the existing NetBackup operator container and record it for later. Run:

   kubectl get pod -n netbackup-operator-system -l nb-control-plane=nb-controller-manager -o jsonpath --template "{.items[*].status.containerStatuses[?(@.name=='netbackup-operator')].imageID}{'\n'}"

   The command prints the name of the image and includes the SHA-256 hash identifying the image. For example:

   exampleacr.azurecr.io/netbackup/operator @sha256:59d4d46d82024a1ab6353 33774c8e19eb5691f3fe988d86ae16a0c5fb636e30c

2. To restart the NetBackup operator, run:

   pod=$(kubectl get pod -n netbackup-operator-system -l nb-control-plane=nb-controller-manager -o jsonpath --template '{.items[*].metadata.name}')

   kubectl delete pod -n netbackup-operator-system $pod

3. Re-run the kubectl command from earlier to get the image ID of the NetBackup operator. Confirm that it's different from what it was before the update.

1. Get the image ID of the existing MSDP Scaleout operator container and save it for later use. Run:

   kubectl get pods -n netbackup-operator-system -l control-plane=controller-manager -o jsonpath --template "{.items[*].status.containerStatuses[?(@.name=='manager')].imageID}{'\n'}"

2. Re-initialize the MSDP Scaleout operator using the new image.

   kubectl msdp init -n netbackup-operator-system --image exampleacr.azurecr.io/msdp-operator:16.0.1-update1

3. Re-run the kubectl command from earlier to get the image ID of the MSDP Scaleout operator. Confirm that it's different from what it was before the update.

1. Look at the list of pods in the application namespace and identify the pod or pods to update. The primary-server pod's name typically end with "primary-0" and media-server pods end with "media-0", "media-1", etc. Hereafter, pod will be referred to as $pod. Run:

   kubectl get pods -n nb-example

2. Get the image ID of the existing NetBackup container and record it for later. Run:

   kubectl get pods -n nb-example $pod -o jsonpath --template "{.status.containerStatuses[*].imageID}{'\n'}"

3. Look at the list of StatefulSets in the application namespace and identify the one that corresponds to the pod or pods to be updated. The name is typically the same as the pod, but without the number at the end. For example, a pod named nb-primary-0 is associated with statefulset nb-primary. Hereafter the statefulset will be referred to as $set. Run:

   kubectl get statefulsets -n nb-example

4. Restart the statefulset. Run:

   kubectl rollout restart -n nb-example statefulset $set

   The pod or pods associated with the statefulset are terminated and be re-created. It may take several minutes to reach the "Running" state.

5. Once the pods are running, re-run the kubectl command from step 2 to get the image ID of the new NetBackup container. Confirm that it's different from what it was before the update.

1. Look at the list of pods in the application namespace and identify the pods to update. The controller pod have "uss-controller" in its name, the MDS pods have "uss-mds" in their names, and the engine pods are be named like their fully qualified domain names. Run:

   kubectl get pods -n nb-example

2. Get the image IDs of the existing MSDP Scaleout containers and record them for later. All the MDS pods use the same image, and all the engine pods use the same image, so it's only necessary to get three image IDs, one for each type of pod.

   kubectl get pods -n nb-example $engine $controller $mds -o jsonpath --template "{range .items[*]}{.status.containerStatuses[*].imageID}{'\n'}{end}"

3. Edit the Environment resource and change the spec.msdpScaleouts[*].tag values to the new tag used earlier in these instructions.

   kubectl edit environment -n nb-example nb-env

   ...
   spec:
     ...
     msdpScaleouts:
     - ...
       tag: "16.0.1-update1"

4. Save the file and close the editor. The MSDP Scaleout pods are terminated and re-created. It may take several minutes for all the pods to reach the "Running" state.
5. Run kubectl get pods, to check the list of pods and note the new name of the uss-controller pod. Then, once the pods are all ready, re-run the kubectl command above to get the image IDs of the new MSDP Scaleout containers. Confirm that they're different from what they were before the update.