PowerProtect Data Manager 19.17 Kubernetes User Guide

PDF

Update the Velero or OADP version used by PowerProtect Data Manager

When PowerProtect Data Manager is configured to protect Kubernetes clusters, Velero is used for backing of Kubernetes resources. In an OpenShift environment, PowerProtect Data manager uses OADP to deploy Velero. Each PowerProtect Data Manager release uses a specific version of Velero by default, which is documented in the file k8s-image-versions.info that is available for download in the PowerProtect Data Manager UI by clicking Settings icon and selecting Downloads. If you must update the Velero or OADP version that PowerProtect Data Manager uses in order to pick up the latest security fixes, perform the following procedure.

Prerequisites

NOTE:The Velero version should be updated to an incremental patch build only. A minor or major version of Velero or OADP that is later than the default version that PowerProtect Data Manager uses might not be compatible.

Steps

  1. Log in to PowerProtect Data Manager as an admin user.
  2. Open the file /usr/local/brs/lib/cndm/config/k8s-dependency-versions-app.properties.
  3. In a non-OpenShift environment, add the following line to this file to update the Velero version, and then save the file:
    k8s.velero.version=vx.y.z

    Where vx.y.z is the Velero incremental patch version.

  4. In an OpenShift environment, add the following line to this file to update the OADP version, and then save the file:
    k8s.oadp.version=x.y.z

    Where x.y.z is the OADP incremental patch version.

  5. Restart the CNDM service by running the command cndm restart, and then wait for a few seconds for the service to restart.
  6. From the PowerProtect Data Manager UI, run a manual discovery of the Kubernetes cluster.
    When the discovery completes successfully, the configuration that is stored in the configuration map ppdm-controller-config on the Kubernetes cluster powerprotect namespace updates.
  7. Run the following commands to delete the powerprotect-controller pod on the Kubernetes cluster. This action forces a restart, during which the changes take effect. This step should be performed when there are no backup or restore operations in progress.
    kubectl get pod -n powerprotect
    kubectl delete pod powerprotect controller pod name -n powerprotect
  8. Repeat steps six and seven for each Kubernetes cluster that the PowerProtect Data Manager protects.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\