Review whether having the operator in a different namespace than the CRs is a problem, there might be some code that assumes that the namespace of the objects is the same namespace than the namespace of the operator. Changing to cluster scope would break that

Review impact at permissions level: what changes regarding roles, clusterroles and what impact does it have when releasing it with OLM?

Review what is the impact of doing a new release with the operator being cluster-role, taking into account existing users: existing users might have one or more operator instances (with namespace mode) in a single cluster, potentially with different apicast versions installed. Maybe this ends up with needing talks to Product team.

Review impact on the upgrades code implementation. Now that the operator is cluster-scoped do upgrades code implementation still work? is the blast radius impact increased?

Review impact on productization. Does it have an impact on the way we release? will our current tagging strategy, replaces/skipRange strategy still work?

Are we going to support both namespaced and cluster scoped operator? what are the implications on each case?