Closed chobostar closed 1 year ago
Each DPA creates/manages a separate Velero instance. The use case for a second DPA would be if you want a separate installation in a completely different namespace, as you can have only one Velero installation in a given namespace.
However, if all you want to do is provide additional backup locations, you don't need a second DPA. Just add a second backup location to the DPA config (with default set to false), and when creating a backup that you want to use the alternate object store, specify this secondary BSL by name when creating the backup CR.
Contact Details
chobostar85@gmail.com
Describe bug
I want to store some backups in separate object storage, so I have created the second DataProtectionApplication:
And I see error
Object openshift-adp/restic-restore-action-config is already owned by another DataProtectionApplication controller mycluster-oadp
, wheremycluster-oadp
is name of firstDataProtectionApplication
I see that
restic-restore-action-config
hardcoded configmap: https://github.com/openshift/oadp-operator/blob/3b9b40f44e74ceac60788c03bf8a0c2fe37cb8b7/controllers/restic.go#L28Is it intended? If so, how to store some filtered backups to separate store? If it's impossible, then how to use oadp-operator in multi-tenant cluster with backups isolation per tenant?
What happened?
Unable to create 2nd
DataProtectionApplication
:where
mycluster-oadp
is name of firstDataProtectionApplication
OADP Version
1.1.1 provided by Red Hat
OpenShift Version
4.11.25
Velero pod logs
No response
Restic pod logs
No response
Operator pod logs
New issue