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

To deploy the operators

1. Install the MSDP kubectl plug-in at some location which is set in the path environment variable of your shell. For example, copy the file kubectl-msdp to/usr/local/bin/.
2. Run the following commands to load each of the product images to the local docker instance.

   $ docker load -i netbackup-main-10.0.0.1.tar.gz

   $ docker load -i netbackup-operator-10.0.0.1.tar.gz

   $ docker load -i pdcluster-16.0.1.tar.gz

   $ docker load -i pdde-16.0.1.tar.gz

   $ docker load -i pdk8soptr-16.0.1.tar.gz

   Run the command docker image ls to confirm that the product images are loaded properly to the docker cache.

3. Run the following commands to re-tag the images to associate them with your container registry.

   $ REGISTRY=<example.azurecr.io> (Replace with your own container registry name)

   $ docker tag netbackup/main:10.0.0.1 ${REGISTRY}/netbackup/main:10.0.0.1

   $ docker tag netbackup/operator:10.0.0.1 ${REGISTRY}/netbackup/operator:10.0.0.1

   $ docker tag uss-engine:16.0.1 ${REGISTRY}/uss-engine:16.0.1

   $ docker tag uss-controller:16.0.1 ${REGISTRY}/uss-controller:16.0.1

   $ docker tag uss-mds:16.0.1 ${REGISTRY}/uss-mds:16.0.1

   $ docker tag msdp-operator:16.0.1 ${REGISTRY}/msdp-operator:16.0.1

4. Run the following commands to push the images to the container registry.

   $ docker push ${REGISTRY}/netbackup/main:10.0.0.1

   $ docker push ${REGISTRY}/netbackup/operator:10.0.0.1

   $ docker push ${REGISTRY}/uss-engine:16.0.1

   $ docker push ${REGISTRY}/uss-controller:16.0.1

   $ docker push ${REGISTRY}/uss-mds:16.0.1

   $ docker push ${REGISTRY}/msdp-operator:16.0.1

5. Create a namespace for deploying the NetBackup and MSDP Scaleout operators. These instructions use the default `netbackup-operator-system` namespace but a custom namespace is also supported, run:

   $ kubectl create namespace netbackup-operator-system

6. Install the MSDP Scaleout operator in the created namespace, using this command. To run this command you must define a full image name in step 3, define a storage class for storing logs from the MSDP operator, and define node selector labels (optional) for scheduling the MSDP operator pod on specific nodes. See Prerequisites.

   $ kubectl msdp init --image ${REGISTRY}/msdp-operator:16.0.1 --storageclass x --namespace netbackup-operator-system -l key1=value1

7. To verify that the MSDP Scaleout operator is running, run:

   $ kubectl get all --namespace netbackup-operator-system

   Here, we are using the namespace created in step 5.

   The msdp-operator pod should show status as Running.

8. In this step, configure the namespace, image name, and node selector to use for the NetBackup operator image by editing the provided configuration yaml files.

   • (Optional) Perform this step only when using a custom namespace. Edit the file operator/kustomization.yaml and change `namespace` to your custom namespace. For example: namespace: my-custom-namespace

   • Edit the file operator/kustomization.yaml and change `newName` and `newTag`. For example:

       images:
            - name: netbackupoperator
              newName: example.com/netbackup/operator
              newTag: '10.0.0.1'

   • Edit the file operator/patches/operator_patch.yaml to add or remove node selectors that control what nodes Kubernetes may schedule the operator to run on. For example:

     nodeSelector:
              nbu_node: 'true'

     If you have no restrictions on pod scheduling, then remove the `nodeSelector` section entirely.

     Note:

     The node/nodegroup for NetBackup operator must be different from that of primary and media server.

9. To install the NetBackup operator, run the following command from the installer's root directory:

   $ kubectl apply -k operator

10. To verify if the NetBackup operator is running, run:

    $ kubectl get all --namespace netbackup-operator-system

    Verify that pod/netbackup-operator STATUS is showing as Running.