Currently our Cluster Ingress Operator (CIO) does not deal with conflicting Subscription resources for OpenShift Service Mesh (OSSM) (see NE-1964).

Some different cases we see as problems that we need to look into:

• Newer version present - What will we do in the future if we support 3.0.0 but 3.1.0 is on the cluster?
• Older version present - What if tech preview is on the cluster, but we need 3.0.0?
• Will older control-plane versions be able to have the subscription upgraded (by us) without disruption?

Can we get improvements in OLM to support this? Does the new ClusterExtension resource have any solutions? Should we consider deploying the Sail Operator ourselves in the CIO? The goal of this spike is to determine how we can get past this limitation.