Proposal: I propose that we collect the packagemanifest details of the ACM and MCE operators that will help us to identify whether the currently installed ACM &MCE versions are compatible with the ocp version or not.

As of now we are needed to refer to the individual ACM version support matrix to identify whether the versions are compatible or not.

For example: From my test ACM hub cluster:

1. # oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.18.29   True        False         26h     Cluster version is 4.18.29

2. [root@vm-232-223 packagemanifests]# oc get packagemanifest advanced-cluster-management -n openshift-marketplace   -o jsonpath='{range .status.channels[*]}{.name}{"\t"}{.currentCSV}{"\n"}{end}'
release-2.12	advanced-cluster-management.v2.12.6
release-2.13	advanced-cluster-management.v2.13.4
release-2.14	advanced-cluster-management.v2.14.1
release-2.15	advanced-cluster-management.v2.15.0

This helps me in understanding that ocp 4.18 is compatible against ACM versions 2.12,2.13,2.14 and 2.15.

This could be achieved by adding this line in the collection_script:

run_inspect packagemanifest/advanced-cluster-management packagemanifest/multicluster-engine -n openshift-marketplace

The ultimate aim is to create an insights rule that automatically evaluates whether the ACM/MCE versions installed by the customer are compatible with the ocp versions are not. This is important because we have faced unpredictable issues when they are not compatible.

If we were to create an insights rule today we will need to rely on static data like a kb article that mentions the list of compatible versions

Let me know your thoughts.