-
Task
-
Resolution: Done
-
Normal
-
OADP 1.2.0
-
None
-
False
-
-
False
-
ToDo
-
-
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Which section(s) is the issue in?
What needs fixing?
There is not enough information about how to use ODF's noobaa as object storage when defining a BackupStorageLocation.
Please considering something like this:h2. ODF Object Bucket Claim apiVersion: objectbucket.io/v1alpha1kind: ObjectBucketClaimmetadata: name: oadp-backup-bucketnamespace: openshift-adplabels: app: noobaabucket-provisioner: openshift-storage.noobaa.io-obcnoobaa-domain: openshift-storage.noobaa.iospec: additionalConfig: bucketclass: noobaa-default-bucket-classbucketName: oadp-backup-bucket-a3800b52-5019-47c9-9d2f-9cdcf9574c65generateBucketName: oadp-backup-bucketobjectBucketName: obc-openshift-adp-oadp-backup-bucketstorageClassName: openshift-storage.noobaa.ioh2. OADP - Velero DPA
apiVersion: oadp.openshift.io/v1alpha1kind: DataProtectionApplicationmetadata: name: velero-dpanamespace: openshift-adpspec: backupImages: falseconfiguration: restic: enable: truevelero: defaultPlugins: - openshift - aws - kubevirt - csifeatureFlags:
- EnableCSInoDefaultBackupLocation: trueh2. Backup Storage Location
apiVersion: velero.io/v1kind: BackupStorageLocationmetadata: name: incluster-bslnamespace: openshift-adpspec: config: profile: defaultregion: noobaas3ForcePathStyle: 'true's3Url: 'https://s3.openshift-storage.svc'insecureSkipTLSVerify: "true"credential: key: cloudname: cloud-credentialsobjectStorage: bucket: oadp-backup-bucket-a3800b52-5019-47c9-9d2f-9cdcf9574c65prefix: valerodefault: trueprovider: aws|
I may have been tagged due to this blog: https://cloud.redhat.com/blog/disaster-recovery-of-virtual-machines-within-openshift . The missing pieces in the documentation are:
- creation of a noobaa bucket for backups (as mentioned)
- creation of a secret to use in the backupStorageLocation|