PowerProtect Data Manager 19.11 Kubernetes User Guide

PDF

Updating PowerProtect Data Manager from version 19.9 or earlier to the latest version in a Kubernetes environment

When updating PowerProtect Data Manager from version 19.9 or earlier to the latest version in a Kubernetes environment, certain considerations must be taken into account.

CAUTION If you are not using the cluster-admin role and you do not follow a Kubernetes-specific update procedure, PowerProtect Data Manager will fail to function properly.

PowerProtect Data Manager uses structural custom resource definitions (CRDs) to extend the Kubernetes API and increase system security. But versions of PowerProtect Data Manager earlier than 19.9 used non-structural schemas that did not validate the consistent format of custom resources (CRs). When updating from a version of PowerProtect Data Manager that supports Kubernetes asset sources to the latest version, certain considerations must be taken into account. For information about updating PowerProtect Data Manager in general, see the PowerProtect Data Manager Administration and User Guide or the PowerProtect Data Manager Deployment Guide.

Self-service recovery

During the update, all CRs are deleted, including the backupjobs CR. After the update, the self-service recovery of the last backup copy taken before the update is not possible. That backup can only be restored from the PowerProtect Data Manager user interface. Self-service recoveries can be performed on backups taken after the update.

Minimum cluster-role privileges

The following cluster roles must have certain privileges:

  • The cluster role bound to the service account provided to PowerProtect Data Manager must have Delete for customresourcedefinitions resources.
  • The cluster role bound to ppdm-serviceaccount must have Patch for deployments resources.

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: <>()\