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. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Patching mechanism for primary, media servers, fluentbit pods, and postgres pods
  5. Overview
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Overview

NetBackup version 10.5 and later provides support for patching the following containers:

  • Primary (main) and its other containers

  • Media

  • Fluentbit container

  • Fluentbit cleanup container

  • PostgreSQL pods

Patching introduces the ability for customers to patch images in a Kubernetes native way by specifying the image tags for respective containers using the serviceImageTag field of the environment. With serviceImageTag only primary server and media server of the environment can be patched.

Note:

Ensure that the required patch images are pushed in the registry.

The poddependency-init image is present inside the operator image, hence to patch poddependency-init image, operator image must be pushed to the registry.

Feedback

Was this page helpful?
Previous

Patching mechanism for primary, media servers, fluentbit pods, and postgres pods

Next

Patching of primary containers

Feedback

Was this page helpful?