How does OpenShift manage potential incompatibilities related to operator versions?

Solution Verified - Updated 2022-03-16T09:26:12+00:00 -

Issue

Is there any mechanism to control whether a specific version of an operator is compatible with a particular OpenShift release?
In case there is a potential incompatibility, would OpenShift block cluster and/or operator upgrades?
Kubernetes 1.22 (and OpenShift 4.9, based on it) will stop serving some deprecated API versions. Will this create potential issues on the functionality of the operators using those versions?
After upgrading the OCP cluster the alert ClusterNotUpgradeable is firing with the following error even if the upgrade finished successfully without any issue.:
```
ClusterServiceVersions blocking cluster upgrade: ${NAMESPACE}/${OPERATOR} is incompatible with OpenShift minor versions greater than 4.X
```

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.