-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
3
-
False
-
-
False
-
ToDo
-
-
-
Important
-
8
-
2.667
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
None
Description of problem:
While the documentation states the following, users imply that there might be a tested/supported way in OADP 1.4 to limit the namespaces for backup/restore targets for each OADP instance as long as the RBAC settings are carefully adjusted.
By default, each OADP deployment has cluster-level access across namespaces. OpenShift Container Platform administrators need to review security and RBAC settings carefully and make any necessary changes to them to ensure that each OADP instance has the correct permissions.
We do not intend to support this scenario as noted in OADP-5043. Therefore, the revision I suggest is to replace above with
By default, each OADP deployment has cluster-level access across namespaces. OpenShift Container Platform administrators need to review potential impacts carefully such as not backing up/restoring from/into the same namespace concurrently.
Following text also needs to replace "project owners" with "cluster admins"
You can install OpenShift API for Data Protection (OADP) into multiple namespaces on the same cluster so that multiple project owners can manage their own OADP instance.
- is triggered by
-
OADP-5043 Need specific examples of RBAC settings for installing OADP in multiple namespaces
- Closed