Upgrade all operators in a given namespace at the same time

This can only be tested on RC, plus we need upgrade available for at least two operators.

As discussed, I have changed the Fix version to 1.2.0.

I don’t think we will be able to test this ticket in release v1.1.0 as both PG and PSMDB operators are not being released this time. We need to move this ticket to the next release.

There are 2 issues here:

1. When patching the catalog source, we should use 1.0.0-rc2 tag, not latest. This is a change we made in this RC. The moment we use latest, OLM will pull in PSMDB 1.16 for existing namespaces. When we upgrade, Everest CLI changes the catalog source back to 1.0.0-rc2, where PSMDB 1.16 is missing. So new namespaces will get 1.15 installed.

2. Assuming that RC2 has both new operator versions available, upgrading one operator should not result in another operator getting upgraded. This is unexpected. On further investigating this scenario, it looks like OLM is the culprit here. When we update the CatalogSource (which contains 2 new operators), it creates a single InstallPlan, that references the 2 new CSVs corresponding to the new versions of the operator. Approving this InstallPlan will result in both operators being upgraded. Unfortunately, this is by design in OLM - that it will aggregate all Subscriptions in its installPlan, meaning we can’t upgrade each operator individually. The complete issue is here - . There’s really not much we can do here, apart from change the Everest UX - instead of giving the user the ability to upgrade each individual operator (which OLM does not allow), we need to instead make it so that all operators are upgraded.