Support for dependency operator to be installed in its own supported namespace #3613
Description
Bug Report
What did you do?
I have a core operator, with some child operators which are different feature sets. Child operators act as standalone products and as dependency of core operator, both.
One of the child operators requires elevated permissions, CRB attached to admin role, where SA namespace is hardcoded for suggested namespace child1-namespace . This rbac breaks when operator is installed as a dependency in a different namespace parent-namespace.
What did you expect to see?
I expect that every child operator gets installed in its own suggested namespace
What did you see instead? Under which circumstances?
CRB was referencing to the suggested namespace of child operator, instead of parent operator
Environment
-
operator-lifecycle-manager version:
quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8857f18845f1aebf044ec78755662bd8fa9fa84efb6cf9e59c1a58f5909cef27 -
Kubernetes version information:
Client Version: v1.32.0
Kustomize Version: v5.5.0
Server Version: v1.31.6
- Kubernetes cluster:
OpenShift 4.18
Possible Solution
I saw OLM v1 has been introduced, but the work is ongoing. I'd like some workaround till OLM v1 is complete
Additional context
Add any other context about the problem here.