Background

Currently, cluster-ingress-operator (CIO) creates a subscription with startingCSV: servicemeshoperator3.v3.0.0 and installPlanApproval: Manual, and then CIO itself lists installplans and approves the one with the desired CSV.

CIO also has logic that updates the subscription if it does not have the expected startingCSV etc.

Requirements

When we bump the desired CSV to servicemeshoperator3.v3.0.1 or newer, CIO should update OSSM by updating the subscription and approving the correct installplan.

We need to verify that OLM creates the expected installplan in this scenario, and that CIO's update logic performs as expected.

We might also need to add logic to diagnose errors (such as missing installplans or a conflicting, user-created subscription). Note that NE-1964 is adding logic to detect conflicting subscriptions; we need to determine whether that work is sufficient in the context of upgrades or whether additional checks are needed.