NetBackup™ Deployment Guide for Kubernetes Clusters

To patch the main, media, poddependency-init container

1. Use the following command to obtain the environment name:

   $ kubectl get environments -n <namespace>

2. Depending on the container, use the following respective command to verify if serviceImageTag is present:

   • For primary container:

     $ kubectl get environment -n <namespace> -o=jsonpath='{$.items[0].spec.primary.serviceImageTag}'

   • For media container:

     $ kubectl get environment -n <namespace> -o=jsonpath='{$.items[0].spec.mediaServers[0].serviceImageTag}'

   • For poddependency-init container:

     $ kubectl get environment -n <namespace> -o=jsonpath='{$.items[0].spec.mediaServers[0].serviceImageTag}'

   Depending on the output perform one of the following:

   If serviceImageTag is present, then run the following command by changing the value field. For example, change 10.5-patch to the required image tag:

   • For primary container:

     $ kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag/primary.main", "value": "10.5-patch"}]'

     For patching init containers of primary server:

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag/<init container keyword>", "value": "10.5-patch"}]'

     For patching sidecar container of primary server

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag/<SideCar containers keyword>", "value": "10.5-patch"}]'

   • For media container:

     $ kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/media.main", "value": "10.5-patch"}]'

     For patching init containers of media server:

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/<Init containers keyword>", "value": "10.5-patch"}]'

     For patching sidecar container of media server

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/<container keyword>", "value": "10.5-patch"}]'

   • For poddependency-init container:

     $ kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/media.pod-dependency-init", "value": "10.5-patch"}]'

   Or

   If serviceImageTag is not present, then run the following command by changing the value field. For example, change 10.5-patch to the required image tag:

   • For primary container:

     $ kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/primary/serviceImageTag/primary.main", "value": "10.5-patch"}]'

     For patching init containers of primary server:

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/primary/serviceImageTag/<init container keyword>", "value": "10.5-patch"}]'

     For patching sidecar container of primary server

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/primary/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/primary/serviceImageTag/<SideCar containers keyword>", "value": "10.5-patch"}]'

   • For media container:

     $ kubectl patch environment nbu -n netbackup --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/media.main", "value": "10.5-patch"}]'

     For patching init containers of media server:

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/<Init containers keyword>", "value": "10.5-patch"}]'

     For patching sidecar container of media server

     kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/<SideCar containers keyword>", "value": "10.5-patch"}]'

   • For poddependency-init container:

     $ kubectl patch environment <env-name> -n <namespace> --type=json --patch '[{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag", "value": {}},{"op": "replace", "path": "/spec/mediaServers/0/serviceImageTag/media.pod-dependency-init", "value": "10.5-patch"}]'

To patch the fluentbit collector pods

1. Using the following command, get the currently configured values. Save the values in a file.

   helm get values -n <namespace> fluentbit | grep -v "USER-SUPPLIED VALUES:" > <values file name>

2. Update the output file to reflect new image tags:

   • Edit and update the tags in below json path file for the fluentbit-collector and execute the command:

     fluentbit.image.tag to 10.5-patch (or actual patch tag)

   • Edit and update the tags in below json path file for the fluenbit-log-cleanup image and execute the command:

     fluentbit.cleanup.image.tag to 10.5-patch (or actual patch tag)

3. To update the deployment, run the helm command:

   helm upgrade --install -n <namespace> fluentbit <fluentbit tgz> -f <values file name>

   Note:

   The tarball you need for this command is the one containing the helm templates, not the docker images. It is usually named fluentbit-<version>.tgz

To update the containerized PostgreSQL pod for NetBackup version 10.5

Consider a scenario - In 10.5-xxxx deployment with netbackup-postgresql version 16.10.x.x, upgrade to netbackup-postgresql version 16.10.x.x using tag 10.5-patch2

1. Suspend the backup job processing using the command:

   nbpemreq -suspend_scheduling

2. Load, tag, and push the new NetBackup PostgreSQL image using the commands:

   To load the PostgreSQL imagedocker load -i VRTSnetbackup-postgresql-16.4.0002.tar.gz

   To load the PostgreSQL-upgrade imagesdocker load -i VRTSnetbackup-postgresql-upgrade-16.4-0002.tar.gz

   To tag the new imagesdocker tag netbackup/postgresql:16.4-0002 exampleacr.azurecr.io/netbackup/postgresql:10.5-patch2

   docker tag localhost/netbackup/postgresql-upgrade:16.4-0002 exampleacr.azurecr.io/netbackup/postgresql-upgrade:10.5_patch2

   To push the PostgreSQL imagedocker push exampleacr.azurecr.io/netbackup/postgresql:10.5-patch2

   docker push exampleacr.azurecr.io/netbackup/postgresql-upgrade:10.5-patch2

3. Upgrade the PostgreSQL using Helm chart:

   To save PostgreSQL chart values to a file: helm show values postgresql-10.5-64.tgz > postgres-values.yaml

   vi postgres-values.yaml

   Upgrade the PostgreSQL: helm upgrade --install postgresql postgresql-10.5-64.tgz -f postgres-values.yaml -n netbackup

4. Resume the backup job processing using the command:

   nbpemreq -resume_scheduling