Docs:

I'm going to write up a FAQ that walks customers, consultants through installing OADP into multiple namespaces.  We'll need to get this expanded and formalized into our official docs.  Multiple customers have been requesting information on the topic in slack, including in a conversation with  Ford 

https://access.redhat.com/articles/5456281#can-i-install-oadp-into-multiple-openshift-projects-to-enable-project-owners-26

QE: test cases are below:

Greetings... New test case required.

Scenario:

Three different teams (A, B, C) share an openshift cluster.  Each team would like manage their own OADP install and backup/restores.

TeamA:  3 apps in namespace team-a1, team-a2, team-a3

TeamB: 2 apps in namespace team-b1, team-b2

TeamC: 1 apps in namespace team-c1

Install OADP into namespace oadp-a, oadp-b, and oadp-c and perform b/r's in the appropriate namespace ensuring that there are no errors in each backups and that each team's own bucket contents only contain team-ax, team-bx, and team-cx contents respectively.

For testing purposes, each team can use the same bucket but a different velero prefix.

Conversation re: customer scenario is found here:

https://redhat-internal.slack.com/archives/C0144ECKUJ0/p1675696198855159