1. Proposed title of this feature request
CMA Operator allows the user of arbitrary namespace name

2. What is the nature and description of the request?
With ROSA/OSD, privileged namespaces are blocked by webhook.  The list is (as of right now in 'master' branch):
https://github.com/openshift/managed-cluster-validating-webhooks/blob/master/pkg/config/namespaces.go#L11-L120

And is documented here: https://docs.openshift.com/rosa/sd_support/rosa-managed-resources.html#rosa-managed-resources-all

From a managed-services/service-delivery perspective there is a strong preference to not rely on a specific namespace for installation, instead support running in any namespace, so that customer has flexibility on how an operator is deployed.

This feature is to gain the ability with the CMA operator to run it in a cluster in a custom named namespace, instead of only "openshift-*" namespaces.

3. Why does the customer need this? (List the business requirements here)

See prior. We have numerous customers eager to use CMA with ROSA/OSD but given the above limitation, we will need this capability.

4. List any affected packages or components.

Unknown