Not able to install the Quay Operator in Openshift 4.18 Cluster because the StackGres Operator was installed on the cluster and StackGres is not present in OperatorHub from 4.18.0    

4.18.0   

Yes    

1. Set up an OpenShift Container Platform (OCP) cluster with version 4.17.

2. Install the latest version of the StackGres Operator (v1.16.2) on the OCP 4.17 cluster.

3. Upgrade the OCP cluster to version 4.18.0.

4. Attempt to install the Quay Operator (v3.14.1).

5. Observe the following error message in the Quay Operator Subscription:
~~~
constraints not satisfiable: no operators found in package stackgres-certified in the catalog referenced by subscription stackgres-certified, subscription stackgres-certified exists
~~~
    

Unable to install the Quay Operator because the StackGres Operator was present on the cluster before upgrading to OpenShift 4.18.0.

The Quay Operator should install successfully on OpenShift 4.18.0, regardless of any previously installed operators on the cluster.

[1] Since the StackGres Operator is a third-party operator and is no longer provided in OpenShift Container Platform (OCP) 4.18 and later, it can cause a problem for customers who have previously installed it and are still using it. In such cases, they may be unable to install the Quay Operator due to the unavailability of the StackGres Operator in the 4.18 channel, which can be a potential blocker.

[2] Currently, the only possible workaround appears to be uninstalling the StackGres Operator before installing the Quay Operator. However, if the customer later wants to reinstall the StackGres Operator, there is no supported way to do so, as it is not available in the 4.18 channel.

[3] Kindly confirm if there is any known correlation or dependency between the StackGres Operator and the Quay Operator that could be affecting this behavior.