Search <book_title>...

NetBackup™ Deployment Guide for Kubernetes Clusters

Last Published: 2025-03-18

Product(s): NetBackup & Alta Data Protection (11.0)

Upgrade fluentbit

For more information on how to save and modify any values during upgrade, refer to the following section:

Parameters for logging (fluentbit)

Note the following

It is recommended to back up all logs before upgrading from NetBackup versions prior to 10.5 (versions prior to the unified fluentbit based logging).
It is recommended to copy and check the differences between the sample and the default fluentbit-values.yaml file.
When upgrading from versions prior to 10.5 to NetBackup version 10.5 or later, the logs would be collected in the fluentbit collector from up to two days prior to the date of the upgrade.
When upgrading from NetBackup 10.5 or later, the logs that exist in the fluentbit collector from the previous release will remain in the fluentbit collector and would continue to be cleaned up as per the configured fluentbit collector cleanup policy.
When upgrading from versions prior to 10.5 and if installing fluentbit for the first time, refer to the following section:
See Deploying fluentbit for logging.
When upgrading to NetBackup version 11.0 or later, ensure that you specify the kubernetes namespaces to collect stdout/stderr logs in the fluentbit.namespaces parameter.
Default values: netbackup, netbackup-operator-system

Depending on the following scenarios, perform the appropriate procedure to upgrade fluentbit:

Upgrade only
Upgrade and modify additional parameters

Upgrade only

If upgrading from a release 10.5 or later, and you do not need to modify parameters other than tags, use the following command:

helm upgrade --install -n netbackup fluentbit fluentbit-<version>.tgz --reuse-values \ --set fluentbit.image.tag=11.0-4163839 \ --set fluentbit.cleanup.image.tag=<version>

Upgrade and modify additional parameters

Perform the following steps to upgrade fluentbit (10.5 or later) when modifying the parameters in addition to the tags:

Note:

It is recommended to copy the following example file and check the differences between the example file and the default fluentbit-values.yaml file.

Use the following command to save the fluentbit chart values to a file:
helm get values -n netbackup fluentbit | tail -n +2 > fluentbit-values.yaml

Use the following command to edit the chart values:

vi fluentbit-values.yaml

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

# Copyright (c) 2025 Veritas Technologies LLC. All rights reserved
global:
  environmentNamespace: "netbackup"
  containerRegistry: "364956537575.dkr.ecr.us-east-1.amazonaws.com"
  timezone: null
  
fluentbit:
  image:
    name: "netbackup/fluentbit"
    tag: 11.0-xxxx
    pullPolicy: IfNotPresent
  
  volume:
    pvcStorage: "100Gi"
    storageClassName: nb-disk-premium
  
  metricsPort: 2020
  
  cleanup:
    image:
      name: "netbackup/fluentbit-log-cleanup"
      tag: 11.0-xxxx
  
    retentionDays: 7
    retentionCleanupTime: '04:00'
  
    # Frequency in minutes
    utilizationCleanupFrequency: 60
  
    # Storage % filled
    highWatermark: 90
    lowWatermark: 60

# Namespaces for pod stdout logs to be collected from 
  namespaces:
  - netbackup
  - netbackup-operator-system
  
# Collector node selector value
collectorNodeSelector:
    node_selector_key: agentpool
    node_selector_value: nbupool
  
# Toleraions Values (key=value:NoSchedule)
tolerations:
  - key: agentpool
    value: nbupool
  - key: agentpool
    value: mediapool
  - key: agentpool
    value: primarypool
  - key: storage-pool
    value: storagepool
  - key: data-plane-pool
    value: dataplanepool

Execute the following command to upgrade the fluentbit deployment:
helm upgrade --install fluentbit fluentbit-<version>.tgz -f fluentbit-values.yaml -n netbackup
Or
If using the OCI container registry, use the following command:
helm install --upgrade fluentbit oci://abcd.veritas.com:5000/helm-charts/fluentbit --version <version> -f fluentbit-values.yaml -n netbackup