Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Kubernetes Administrator's Guide
  3. Deploying and configuring the NetBackup Kubernetes operator
  4. Upgrade the NetBackup Kubernetes operator
NetBackup™ for Kubernetes Administrator's Guide

Upgrade the NetBackup Kubernetes operator

You can upgrade the NetBackup Kubernetes operator deployment using Helm commands.

Example:

helm upgrade veritas-netbackupkops ./netbackupkops-helm-chart -n netbackup

Rolling upgrade

The Kubernetes protection follows the standard NetBackup upgrade approach and supports rolling upgrades.

This means you can upgrade the Kubernetes operator and NetBackup servers in stages instead of upgrading everything at the same time. During an upgrade, the operator and data mover can run one version behind the Media Server and up to two versions behind the Primary Server.

When different versions are used, only the features available in the operator's version are supported.

The rolling upgrade support is available from Netbackup primary server version 11.0 onwards.

  • Existing policies continue to take backups but must be restored manually until the Kubernetes operator is updated.

    Note:

    This is applicable to the NetBackup version 9.1 to 10.x upgrade

To upgrade the NetBackup Kubernetes operator

  1. Download the tar package from Cohesity Technical Support website: https://support.cohesity.com/s/
  2. Extract the package to the home directory. The netbackupkops-helm-chart folder must be in the home directory.
  3. To list all cluster contexts, run the command: kubectl config get-contexts
  4. To switch to the cluster where you want to deploy the operator service, run the command:kubectl config use-context <cluster-context-name>
  5. To change the current directory to your home directory, run the command: cd ~
  6. NetBackup supports any Container Image Repositories complied to OCI standards. you can use any tools to push the operators and data mover images. If you use a private docker registry, follow the instructions in this step to create a secret nb-docker-cred in NetBackup namespace. Otherwise, skip to the next step.
    • To load the image to the docker cache and push the image to the docker image repository, run the commands:

      • Load the tar file for Netbackup Kubernetes operator.

        <docker load -i <nameof the tar file> ./>

      • Tag the loaded docker image as per requirement.

        docker tag <imagename:tagof the loadedimage> <repo-name/image-name:tag-name>

      • Push the image to a repository from where Kubernetes can fetch the image at the time of NetBackup Kubernetes operator deployment.

        docker push <repo-name/image-name:tag-name>

    Note:

    In the example, a docker is used for reference. You can use any other CLI tool that provides equivalent functionality.

  7. Edit the netbackupkops-helm-chart/values.yaml in a text editor:

    • Replace the image value in the manager section with your image name and tag in the format reponame/image-name:tag-name.

    • Replace the datamover image in the netbackup_config_pod section with datamover image name and tag.

  8. To upgrade the NetBackup Kubernetes operator, run the command:

    helm upgrade <plugin-name> <chart-path> -n <namespace>

    Example:

    helm upgrade veritas-netbackupkops ./netbackupkops-helm-chart -n netbackup

    Note:

    Upgrading the NetBackup Kubernetes operator will reset the Helm values to their defaults. Ensure that you back up the old configmap and reapply any patches if the values change after the upgrade.

Feedback

Was this page helpful?
Previous

Port requirements for Kubernetes workload

Next

Delete the NetBackup Kubernetes operator

Feedback

Was this page helpful?