Configuring the OpenShift API for Data Protection with Google Cloud Platform

You install the OpenShift API for Data Protection (OADP) with Google Cloud Platform (GCP) by installing the OADP Operator. The Operator installs Velero 1.12.

Starting from OADP 1.0.4, all OADP 1.0.z versions can only be used as a dependency of the MTC Operator and are not available as a standalone Operator.

You configure GCP for Velero, create a default Secret, and then install the Data Protection Application. For more details, see Installing the OADP Operator.

To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See Using Operator Lifecycle Manager on restricted networks for details.

Configuring Google Cloud Platform

You configure Google Cloud Platform (GCP) for the OpenShift API for Data Protection (OADP).

Prerequisites

Procedure

  1. Log in to GCP:

    1. $ gcloud auth login

  2. Set the BUCKET variable:

    1. $ BUCKET=<bucket> (1)
    1Specify your bucket name.

  3. Create the storage bucket:

    1. $ gsutil mb gs://$BUCKET/

  4. Set the PROJECT_ID variable to your active project:

    1. $ PROJECT_ID=$(gcloud config get-value project)

  5. Create a service account:

    1. $ gcloud iam service-accounts create velero \
    2.     --display-name "Velero service account"

  6. List your service accounts:

    1. $ gcloud iam service-accounts list

  7. Set the SERVICE_ACCOUNT_EMAIL variable to match its email value:

    1. $ SERVICE_ACCOUNT_EMAIL=$(gcloud iam service-accounts list \
    2.     --filter="displayName:Velero service account" \
    3.     --format 'value(email)')

  8. Attach the policies to give the velero user the minimum necessary permissions:

    1. $ ROLE_PERMISSIONS=(
    2.     compute.disks.get
    3.     compute.disks.create
    4.     compute.disks.createSnapshot
    5.     compute.snapshots.get
    6.     compute.snapshots.create
    7.     compute.snapshots.useReadOnly
    8.     compute.snapshots.delete
    9.     compute.zones.get
    10.     storage.objects.create
    11.     storage.objects.delete
    12.     storage.objects.get
    13.     storage.objects.list
    14.     iam.serviceAccounts.signBlob
    15. )

  9. Create the velero.server custom role:

    1. $ gcloud iam roles create velero.server \
    2.     --project $PROJECT_ID \
    3.     --title "Velero Server" \
    4.     --permissions "$(IFS=","; echo "${ROLE_PERMISSIONS[*]}")"

  10. Add IAM policy binding to the project:

    1. $ gcloud projects add-iam-policy-binding $PROJECT_ID \
    2.    --member serviceAccount:$SERVICE_ACCOUNT_EMAIL \
    3.    --role projects/$PROJECT_ID/roles/velero.server

  11. Update the IAM service account:

    1. $ gsutil iam ch serviceAccount:$SERVICE_ACCOUNT_EMAIL:objectAdmin gs://${BUCKET}

  12. Save the IAM service account keys to the credentials-velero file in the current directory:

    1. $ gcloud iam service-accounts keys create credentials-velero \
    2.    --iam-account $SERVICE_ACCOUNT_EMAIL

    You use the credentials-velero file to create a Secret object for GCP before you install the Data Protection Application.

About backup and snapshot locations and their secrets

You specify backup and snapshot locations and their secrets in the DataProtectionApplication custom resource (CR).

Backup locations

You specify AWS S3-compatible object storage, such as Multicloud Object Gateway or MinIO, as a backup location.

Velero backs up OKD resources, Kubernetes objects, and internal images as an archive file on object storage.

Snapshot locations

If you use your cloud provider’s native snapshot API to back up persistent volumes, you must specify the cloud provider as the snapshot location.

If you use Container Storage Interface (CSI) snapshots, you do not need to specify a snapshot location because you will create a VolumeSnapshotClass CR to register the CSI driver.

If you use File System Backup (FSB), you do not need to specify a snapshot location because FSB backs up the file system on object storage.

Secrets

If the backup and snapshot locations use the same credentials or if you do not require a snapshot location, you create a default Secret.

If the backup and snapshot locations use different credentials, you create two secret objects:

  • Custom Secret for the backup location, which you specify in the DataProtectionApplication CR.

  • Default Secret for the snapshot location, which is not referenced in the DataProtectionApplication CR.

The Data Protection Application requires a default Secret. Otherwise, the installation will fail.

If you do not want to specify backup or snapshot locations during the installation, you can create a default Secret with an empty credentials-velero file.

Creating a default Secret

You create a default Secret if your backup and snapshot locations use the same credentials or if you do not require a snapshot location.

The default name of the Secret is cloud-credentials-gcp.

The DataProtectionApplication custom resource (CR) requires a default Secret. Otherwise, the installation will fail. If the name of the backup location Secret is not specified, the default name is used.

If you do not want to use the backup location credentials during the installation, you can create a Secret with the default name by using an empty credentials-velero file.

Prerequisites

  • Your object storage and cloud storage, if any, must use the same credentials.

  • You must configure object storage for Velero.

  • You must create a credentials-velero file for the object storage in the appropriate format.

Procedure

  • Create a Secret with the default name:

    1. $ oc create secret generic cloud-credentials-gcp -n openshift-adp --from-file cloud=credentials-velero

The Secret is referenced in the spec.backupLocations.credential block of the DataProtectionApplication CR when you install the Data Protection Application.

Creating secrets for different credentials

If your backup and snapshot locations use different credentials, you must create two Secret objects:

  • Backup location Secret with a custom name. The custom name is specified in the spec.backupLocations block of the DataProtectionApplication custom resource (CR).

  • Snapshot location Secret with the default name, cloud-credentials-gcp. This Secret is not specified in the DataProtectionApplication CR.

Procedure

  1. Create a credentials-velero file for the snapshot location in the appropriate format for your cloud provider.

  2. Create a Secret for the snapshot location with the default name:

    1. $ oc create secret generic cloud-credentials-gcp -n openshift-adp --from-file cloud=credentials-velero

  3. Create a credentials-velero file for the backup location in the appropriate format for your object storage.

  4. Create a Secret for the backup location with a custom name:

    1. $ oc create secret generic <custom_secret> -n openshift-adp --from-file cloud=credentials-velero

  5. Add the Secret with the custom name to the DataProtectionApplication CR, as in the following example:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. metadata:
    4.   name: <dpa_sample>
    5.   namespace: openshift-adp
    6. spec:
    7. ...
    8.   backupLocations:
    9.     - velero:
    10.         provider: gcp
    11.         default: true
    12.         credential:
    13.           key: cloud
    14.           name: <custom_secret> (1)
    15.         objectStorage:
    16.           bucket: <bucket_name>
    17.           prefix: <prefix>
    18.   snapshotLocations:
    19.     - velero:
    20.         provider: gcp
    21.         default: true
    22.         config:
    23.           project: <project>
    24.           snapshotLocation: us-west1
    1Backup location Secret with custom name.

Configuring the Data Protection Application

You can configure the Data Protection Application by setting Velero resource allocations or enabling self-signed CA certificates.

Setting Velero CPU and memory resource allocations

You set the CPU and memory resource allocations for the Velero pod by editing the DataProtectionApplication custom resource (CR) manifest.

Prerequisites

  • You must have the OpenShift API for Data Protection (OADP) Operator installed.

Procedure

  • Edit the values in the spec.configuration.velero.podConfig.ResourceAllocations block of the DataProtectionApplication CR manifest, as in the following example:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. metadata:
    4.   name: <dpa_sample>
    5. spec:
    6. ...
    7.   configuration:
    8.     velero:
    9.       podConfig:
    10.         nodeSelector: <node selector> (1)
    11.         resourceAllocations: (2)
    12.           limits:
    13.             cpu: "1"
    14.             memory: 1024Mi
    15.           requests:
    16.             cpu: 200m
    17.             memory: 256Mi
    1Specify the node selector to be supplied to Velero podSpec.
    2The resourceAllocations listed are for average usage.

Kopia is an option in OADP 1.3 and later releases. You can use Kopia for file system backups, and Kopia is your only option for Data Mover cases with the built-in Data Mover.

Kopia is more resource intensive than Restic, and you might need to adjust the CPU and memory requirements accordingly.

Enabling self-signed CA certificates

You must enable a self-signed CA certificate for object storage by editing the DataProtectionApplication custom resource (CR) manifest to prevent a certificate signed by unknown authority error.

Prerequisites

  • You must have the OpenShift API for Data Protection (OADP) Operator installed.

Procedure

  • Edit the spec.backupLocations.velero.objectStorage.caCert parameter and spec.backupLocations.velero.config parameters of the DataProtectionApplication CR manifest:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. metadata:
    4.   name: <dpa_sample>
    5. spec:
    6. ...
    7.   backupLocations:
    8.     - name: default
    9.       velero:
    10.         provider: aws
    11.         default: true
    12.         objectStorage:
    13.           bucket: <bucket>
    14.           prefix: <prefix>
    15.           caCert: <base64_encoded_cert_string> (1)
    16.         config:
    17.           insecureSkipTLSVerify: "false" (2)
    18. ...
    1Specify the Base64-encoded CA certificate string.
    2The insecureSkipTLSVerify configuration can be set to either “true” or “false”. If set to “true”, SSL/TLS security is disabled. If set to “false”, SSL/TLS security is enabled.

Installing the Data Protection Application 1.2 and earlier

You install the Data Protection Application (DPA) by creating an instance of the DataProtectionApplication API.

Prerequisites

  • You must install the OADP Operator.

  • You must configure object storage as a backup location.

  • If you use snapshots to back up PVs, your cloud provider must support either a native snapshot API or Container Storage Interface (CSI) snapshots.

  • If the backup and snapshot locations use the same credentials, you must create a Secret with the default name, cloud-credentials-gcp.

  • If the backup and snapshot locations use different credentials, you must create two Secrets:

    • Secret with a custom name for the backup location. You add this Secret to the DataProtectionApplication CR.

    • Secret with another custom name for the snapshot location. You add this Secret to the DataProtectionApplication CR.

      If you do not want to specify backup or snapshot locations during the installation, you can create a default Secret with an empty credentials-velero file. If there is no default Secret, the installation will fail.

      Velero creates a secret named velero-repo-credentials in the OADP namespace, which contains a default backup repository password. You can update the secret with your own password encoded as base64 before you run your first backup targeted to the backup repository. The value of the key to update is Data[repository-password].

      After you create your DPA, the first time that you run a backup targeted to the backup repository, Velero creates a backup repository whose secret is velero-repo-credentials, which contains either the default password or the one you replaced it with. If you update the secret password after the first backup, the new password will not match the password in velero-repo-credentials, and therefore, Velero will not be able to connect with the older backups.

Procedure

  1. Click Operators → Installed Operators and select the OADP Operator.

  2. Under Provided APIs, click Create instance in the DataProtectionApplication box.

  3. Click YAML View and update the parameters of the DataProtectionApplication manifest:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. metadata:
    4.   name: <dpa_sample>
    5.   namespace: openshift-adp
    6. spec:
    7.   configuration:
    8.     velero:
    9.       defaultPlugins:
    10.         - gcp
    11.         - openshift (1)
    12.       resourceTimeout: 10m (2)
    13.     restic:
    14.       enable: true (3)
    15.       podConfig:
    16.         nodeSelector: <node_selector> (4)
    17.   backupLocations:
    18.     - velero:
    19.         provider: gcp
    20.         default: true
    21.         credential:
    22.           key: cloud (5)
    23.           name: cloud-credentials-gcp (6)
    24.         objectStorage:
    25.           bucket: <bucket_name> (7)
    26.           prefix: <prefix> (8)
    27.   snapshotLocations: (9)
    28.     - velero:
    29.         provider: gcp
    30.         default: true
    31.         config:
    32.           project: <project>
    33.           snapshotLocation: us-west1 (10)
    1The openshift plugin is mandatory.
    2Specify how many minutes to wait for several Velero resources before timeout occurs, such as Velero CRD availability, volumeSnapshot deletion, and backup repository availability. The default is 10m.
    3Set this value to false if you want to disable the Restic installation. Restic deploys a daemon set, which means that Restic pods run on each working node. In OADP version 1.2 and later, you can configure Restic for backups by adding spec.defaultVolumesToFsBackup: true to the Backup CR. In OADP version 1.1, add spec.defaultVolumesToRestic: true to the Backup CR.
    4Specify on which nodes Restic is available. By default, Restic runs on all nodes.
    5Secret key that contains credentials. For Google workload identity federation cloud authentication use service_account.json.
    6Secret name that contains credentials. If you do not specify this value, the default name, cloud-credentials-gcp, is used.
    7Specify a bucket as the backup storage location. If the bucket is not a dedicated bucket for Velero backups, you must specify a prefix.
    8Specify a prefix for Velero backups, for example, velero, if the bucket is used for multiple purposes.
    9Specify a snapshot location, unless you use CSI snapshots or Restic to back up PVs.
    10The snapshot location must be in the same region as the PVs.

  4. Click Create.

Verifying the installation

  1. Verify the installation by viewing the OpenShift API for Data Protection (OADP) resources by running the following command:

    1. $ oc get all -n openshift-adp

    Example output

    1. NAME                                                     READY   STATUS    RESTARTS   AGE
    2. pod/oadp-operator-controller-manager-67d9494d47-6l8z8    2/2     Running   0          2m8s
    3. pod/restic-9cq4q                                         1/1     Running   0          94s
    4. pod/restic-m4lts                                         1/1     Running   0          94s
    5. pod/restic-pv4kr                                         1/1     Running   0          95s
    6. pod/velero-588db7f655-n842v                              1/1     Running   0          95s
    8. NAME                                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
    9. service/oadp-operator-controller-manager-metrics-service   ClusterIP   172.30.70.140    <none>        8443/TCP   2m8s
    11. NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
    12. daemonset.apps/restic   3         3         3       3            3           <none>          96s
    14. NAME                                                READY   UP-TO-DATE   AVAILABLE   AGE
    15. deployment.apps/oadp-operator-controller-manager    1/1     1            1           2m9s
    16. deployment.apps/velero                              1/1     1            1           96s
    18. NAME                                                           DESIRED   CURRENT   READY   AGE
    19. replicaset.apps/oadp-operator-controller-manager-67d9494d47    1         1         1       2m9s
    20. replicaset.apps/velero-588db7f655                              1         1         1       96s

  2. Verify that the DataProtectionApplication (DPA) is reconciled by running the following command:

    1. $ oc get dpa dpa-sample -n openshift-adp -o jsonpath='{.status}'

    Example output

    1. {"conditions":[{"lastTransitionTime":"2023-10-27T01:23:57Z","message":"Reconcile complete","reason":"Complete","status":"True","type":"Reconciled"}]}

  3. Verify the type is set to Reconciled.

  4. Verify the backup storage location and confirm that the PHASE is Available by running the following command:

    1. $ oc get backupStorageLocation -n openshift-adp

    Example output

    1. NAME           PHASE       LAST VALIDATED   AGE     DEFAULT
    2. dpa-sample-1   Available   1s               3d16h   true

Google workload identity federation cloud authentication

Applications running outside Google Cloud use service account keys, such as usernames and passwords, to gain access to Google Cloud resources. These service account keys might become a security risk if they are not properly managed.

With Google’s workload identity federation, you can use Identity and Access Management (IAM) to offer IAM roles, including the ability to impersonate service accounts, to external identities. This eliminates the maintenance and security risks associated with service account keys.

Workload identity federation handles encrypting and decrypting certificates, extracting user attributes, and validation. Identity federation externalizes authentication, passing it over to Security Token Services (STS), and reduces the demands on individual developers. Authorization and controlling access to resources remain the responsibility of the application.

Google workload identity federation is available for OADP 1.3.x and later.

For backing up volumes, OADP on GCP with Google workload identity federation authentication supports only CSI snapshots.

If you do not use Google workload identity federation cloud authentication, continue to Installing the Data Protection Application.

Prerequisites

  • You have installed a cluster in manual mode with GCP Workload Identity configured.

  • You have access to the Cloud Credential Operator utility (ccoctl) and to the associated workload identity pool.

Procedure

  1. Create an oadp-credrequest directory by running the following command:

    1. $ mkdir -p oadp-credrequest

  2. Create a CredentialsRequest.yaml file as following:

    1. echo 'apiVersion: cloudcredential.openshift.io/v1
    2. kind: CredentialsRequest
    3. metadata:
    4.   name: oadp-operator-credentials
    5.   namespace: openshift-cloud-credential-operator
    6. spec:
    7.   providerSpec:
    8.     apiVersion: cloudcredential.openshift.io/v1
    9.     kind: GCPProviderSpec
    10.     permissions:
    11.     - compute.disks.get
    12.     - compute.disks.create
    13.     - compute.disks.createSnapshot
    14.     - compute.snapshots.get
    15.     - compute.snapshots.create
    16.     - compute.snapshots.useReadOnly
    17.     - compute.snapshots.delete
    18.     - compute.zones.get
    19.     - storage.objects.create
    20.     - storage.objects.delete
    21.     - storage.objects.get
    22.     - storage.objects.list
    23.     - iam.serviceAccounts.signBlob
    24.     skipServiceCheck: true
    25.   secretRef:
    26.     name: cloud-credentials-gcp
    27.     namespace: <OPERATOR_INSTALL_NS>
    28.   serviceAccountNames:
    29.   - velero
    30. ' > oadp-credrequest/credrequest.yaml

  3. Use the ccoctl utility to process the CredentialsRequest objects in the oadp-credrequest directory by running the following command:

    1. $ ccoctl gcp create-service-accounts \
    2.     --name=<name> \
    3.     --project=<gcp_project_id> \
    4.     --credentials-requests-dir=oadp-credrequest \
    5.     --workload-identity-pool=<pool_id> \
    6.     --workload-identity-provider=<provider_id>

    The manifests/openshift-adp-cloud-credentials-gcp-credentials.yaml file is now available to use in the following steps.

  4. Create a namespace by running the following command:

    1. $ oc create namespace <OPERATOR_INSTALL_NS>

  5. Apply the credentials to the namespace by running the following command:

    1. $ oc apply -f manifests/openshift-adp-cloud-credentials-gcp-credentials.yaml

Installing the Data Protection Application 1.3

You install the Data Protection Application (DPA) by creating an instance of the DataProtectionApplication API.

Prerequisites

  • You must install the OADP Operator.

  • You must configure object storage as a backup location.

  • If you use snapshots to back up PVs, your cloud provider must support either a native snapshot API or Container Storage Interface (CSI) snapshots.

  • If the backup and snapshot locations use the same credentials, you must create a Secret with the default name, cloud-credentials-gcp.

  • If the backup and snapshot locations use different credentials, you must create two Secrets:

    • Secret with a custom name for the backup location. You add this Secret to the DataProtectionApplication CR.

    • Secret with another custom name for the snapshot location. You add this Secret to the DataProtectionApplication CR.

      If you do not want to specify backup or snapshot locations during the installation, you can create a default Secret with an empty credentials-velero file. If there is no default Secret, the installation will fail.

Procedure

  1. Click Operators → Installed Operators and select the OADP Operator.

  2. Under Provided APIs, click Create instance in the DataProtectionApplication box.

  3. Click YAML View and update the parameters of the DataProtectionApplication manifest:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. metadata:
    4.   name: <dpa_sample>
    5.   namespace: <OPERATOR_INSTALL_NS> (1)
    6. spec:
    7.   configuration:
    8.     velero:
    9.       defaultPlugins:
    10.         - gcp
    11.         - openshift (2)
    12.       resourceTimeout: 10m (3)
    13.     nodeAgent: (4)
    14.       enable: true (5)
    15.       uploaderType: kopia (6)
    16.       podConfig:
    17.         nodeSelector: <node_selector> (7)
    18.   backupLocations:
    19.     - velero:
    20.         provider: gcp
    21.         default: true
    22.         credential:
    23.           key: cloud (8)
    24.           name: cloud-credentials-gcp (9)
    25.         objectStorage:
    26.           bucket: <bucket_name> (10)
    27.           prefix: <prefix> (11)
    28.   snapshotLocations: (12)
    29.     - velero:
    30.         provider: gcp
    31.         default: true
    32.         config:
    33.           project: <project>
    34.           snapshotLocation: us-west1 (13)
    1The default namespace for OADP is openshift-adp. The namespace is a variable and is configurable.
    2The openshift plugin is mandatory.
    3Specify how many minutes to wait for several Velero resources before timeout occurs, such as Velero CRD availability, volumeSnapshot deletion, and backup repository availability. The default is 10m.
    4The administrative agent that routes the administrative requests to servers.
    5Set this value to true if you want to enable nodeAgent and perform File System Backup.
    6Enter kopia or restic as your uploader. You cannot change the selection after the installation. For the Built-in DataMover you must use Kopia. The nodeAgent deploys a daemon set, which means that the nodeAgent pods run on each working node. You can configure File System Backup by adding spec.defaultVolumesToFsBackup: true to the Backup CR.
    7Specify the nodes on which Kopia or Restic are available. By default, Kopia or Restic run on all nodes.
    8Secret key that contains credentials. For Google workload identity federation cloud authentication use service_account.json.
    9Secret name that contains credentials. If you do not specify this value, the default name, cloud-credentials-gcp, is used.
    10Specify a bucket as the backup storage location. If the bucket is not a dedicated bucket for Velero backups, you must specify a prefix.
    11Specify a prefix for Velero backups, for example, velero, if the bucket is used for multiple purposes.
    12Specify a snapshot location, unless you use CSI snapshots or Restic to back up PVs.
    13The snapshot location must be in the same region as the PVs.

  4. Click Create.

Verifying the installation

  1. Verify the installation by viewing the OpenShift API for Data Protection (OADP) resources by running the following command:

    1. $ oc get all -n openshift-adp

    Example output

    1. NAME                                                     READY   STATUS    RESTARTS   AGE
    2. pod/oadp-operator-controller-manager-67d9494d47-6l8z8    2/2     Running   0          2m8s
    3. pod/node-agent-9cq4q                                     1/1     Running   0          94s
    4. pod/node-agent-m4lts                                     1/1     Running   0          94s
    5. pod/node-agent-pv4kr                                     1/1     Running   0          95s
    6. pod/velero-588db7f655-n842v                              1/1     Running   0          95s
    8. NAME                                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
    9. service/oadp-operator-controller-manager-metrics-service   ClusterIP   172.30.70.140    <none>        8443/TCP   2m8s
    10. service/openshift-adp-velero-metrics-svc                   ClusterIP   172.30.10.0      <none>        8085/TCP   8h
    12. NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
    13. daemonset.apps/node-agent    3         3         3       3            3           <none>          96s
    15. NAME                                                READY   UP-TO-DATE   AVAILABLE   AGE
    16. deployment.apps/oadp-operator-controller-manager    1/1     1            1           2m9s
    17. deployment.apps/velero                              1/1     1            1           96s
    19. NAME                                                           DESIRED   CURRENT   READY   AGE
    20. replicaset.apps/oadp-operator-controller-manager-67d9494d47    1         1         1       2m9s
    21. replicaset.apps/velero-588db7f655                              1         1         1       96s

  2. Verify that the DataProtectionApplication (DPA) is reconciled by running the following command:

    1. $ oc get dpa dpa-sample -n openshift-adp -o jsonpath='{.status}'

    Example output

    1. {"conditions":[{"lastTransitionTime":"2023-10-27T01:23:57Z","message":"Reconcile complete","reason":"Complete","status":"True","type":"Reconciled"}]}

  3. Verify the type is set to Reconciled.

  4. Verify the backup storage location and confirm that the PHASE is Available by running the following command:

    1. $ oc get backupStorageLocation -n openshift-adp

    Example output

    1. NAME           PHASE       LAST VALIDATED   AGE     DEFAULT
    2. dpa-sample-1   Available   1s               3d16h   true

Enabling CSI in the DataProtectionApplication CR

You enable the Container Storage Interface (CSI) in the DataProtectionApplication custom resource (CR) in order to back up persistent volumes with CSI snapshots.

Prerequisites

  • The cloud provider must support CSI snapshots.

Procedure

  • Edit the DataProtectionApplication CR, as in the following example:

    1. apiVersion: oadp.openshift.io/v1alpha1
    2. kind: DataProtectionApplication
    3. ...
    4. spec:
    5.   configuration:
    6.     velero:
    7.       defaultPlugins:
    8.       - openshift
    9.       - csi (1)
    1Add the csi default plugin.