Goal: Prepare existing OLM APIs and workflows to support a global singleton Operator model in the future

Benefits hypothesis: The transition to a global singleton Operator model as well as the Operator API brings in a large set of changes to the OLM experience. In order to provide a smooth transition for existing customers a certain subset of those features can be made available with the current APIs which already address current pain points.

Why is this important: There are certain aspects of the current OLM APIs and operational workflows that cause customers to use OLM in a way that make them prefer scoped Operators. Examples are excessive copying of CSVs for descoped Operators or lack of controls for RBAC. If this can be addressed in the current state of OLM it helps making the switch to descoped Operators less disruptive for customers, because only an insignificant minority of customers would still use scoped Operators.

Expected deliverables:

• a new Operator discovery and availability mechanisms for tenants that scales with the cluster size
• a way for cluster admins to control Operator RBAC independently of their scope / visibility of tenants