-
Bug
-
Resolution: Obsolete
-
Critical
-
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 are unclear on how to set up this RBAC settings concretely.
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 need clear examples. For instance, here is the use case that some users are considering:
TeamA: Installs OADP into namespace oadp-a, and wants to backup/restore namespace team-a, but don't want to allow backup/restore of other namespaces. TeamB: Installs OADP into namespace oadp-b, and wants to backup/restore namespace team-b, but don't want to allow backup/restore of other namespaces.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
also update https://access.redhat.com/articles/5456281#can-i-install-oadp-into-multiple-openshift-projects-to-enable-project-owners-31 when this ticket is done.