NetBackup™ Deployment Guide for Kubernetes Clusters

Upgrading the NetBackup operator

1. Push the new operator images, NetBackup main image, NetBackup media image to container registry with different tags.
2. Run the following script when upgrading from an earlier release of Cloud Scale that used a single helm chart or the kustomize deployment method:

   scripts/prep_operators_for_upgrade.sh

3. Use the following command to suspend the backup job processing:

   nbpemreq -suspend_scheduling

4. Perform the following steps to upgrade the operators:

   • Use the following command to save the operators chart values to a file:

     # helm show values operators-<version>.tgz > operators-values.yaml

   • Use the following command to edit the chart values to match your deployment scenario:

     # vi operators-values.yaml

   • Execute the following command to upgrade the operators:

     helm upgrade --install operators operators-<version>.tgz -f operators-values.yaml -n netbackup-operator-system

     Or

     If using the OCI registry, use the following command:

     helm upgrade --install operators oci://abcd.veritas.com:5000/helm-charts/operators --version <version> -f operators-values.yaml -n netbackup-operator-system

   Following is an example for operators-values.yaml file:

   # Copyright (c) 2023 Veritas Technologies LLC. All rights reserved
    
   # Default values for operators.
   # This is a YAML-formatted file.
   # Declare variables to be passed into your templates.
    
   global:
     # Toggle for platform-specific features & settings
     # Microsoft AKS: "aks"
     # Amazon EKS: "eks"
     platform: "eks"
     # This specifies a container registry that the cluster has access to.
     # NetBackup images should be pushed to this registry prior to applying this
     # Environment resource.
     # Example Azure Container Registry name:
     # example.azurecr.io
     # Example AWS Elastic Container Registry name:
     # 123456789012.dkr.ecr.us-east-1.amazonaws.com
     containerRegistry: "364956537575.dkr.ecr.us-east-1.amazonaws.com"
     operatorNamespace: "netbackup-operator-system"
    
     storage:
       eks:
         fileSystemId: fs-0f3cc640eeec507d0
    
   msdp-operator:
     image:
       name: msdp-operator
       # Provide tag value in quotes eg: '17.0'
       tag: "20.4"
       pullPolicy: Always
    
     namespace:
       labels:
         control-plane: controller-manager
    
     # This determines the path used for storing core files in the case of a crash.
     corePattern: "/core/core.%e.%p.%t"
    
     # This specifies the number of replicas of the msdp-operator controllers
     # to create. Minimum number of supported replicas is 1.
     replicas: 2
     # Optional: provide label selectors to dictate pod scheduling on nodes.
     # By default, when given an empty {} all nodes will be equally eligible.
     # Labels should be given as key-value pairs, ex:
     #   agentpool: mypoolname
     nodeSelector: {}
    
     # Storage specification to be used by underlying persistent volumes.
     # References entries in global.storage by default, but can be replaced
     storageClass:
       name: nb-disk-premium
       size: 5Gi
    
     # Specify how much of each resource a container needs.
     resources:
       # Requests are used to decide which node(s) should be scheduled for pods.
       # Pods may use more resources than specified with requests.
       requests:
         cpu: 150m
         memory: 150Mi
       # Optional: Limits can be implemented to control the maximum utilization by pods.
       # The runtime prevents the container from using more than the configured resource limits.
       limits: {}
    
     logging:
       # Enable verbose logging
       debug: false
       # Maximum age (in days) to retain log files, 1 <= N <= 365
       age: 28
       # Maximum number of log files to retain, 1 <= N =< 20
       num: 20
    
   nb-operator:
     image:
       name: "netbackup/operator"
       tag: "10.4"
       pullPolicy: Always
    
     # nb-operator needs to know the version of msdp and flexsnap operators for webhook
     # to do version checking
     msdp-operator:
       image:
         tag: "20.4"
    
     flexsnap-operator:
       image:
         tag: "10.4.0.0.1016"
    
     namespace:
       labels:
         nb-control-plane: nb-controller-manager
    
     nodeSelector:
       node_selector_key: agentpool
       node_selector_value: agentpool
    
     #loglevel:
     #  "-1" - Debug (not recommended for production)
     #  "0"  - Info
     #  "1"  - Warn
     #  "2"  - Error
    
     loglevel:
       value: "0"
    
   flexsnap-operator:
     replicas: 1
    
     namespace:
       labels: {}
    
     image:
       name: "veritas/flexsnap-deploy"
       tag: "10.4.0.1004"
       pullPolicy: Always
    
     nodeSelector:
       node_selector_key: agentpool
       node_selector_value: agentpool