Description of problem:

In the MCE support matrix, we state that MCE does not support provisioning a hosted cluster with N+1 version based on the hypershift operator version.

For example, the hypershift operator version that is shipped with MCE 2.4 is 4.14. The HO version that is shipped with MCE 2.5 is 4.15. MCE 2.6 will have HO 4.16... and so on. The hypershift operator version is pinned with MCE version.

This means, MCE 2.4 can provision and upgrade hosted clusters with OCP 4.14.z.

MCE 2.5 can provision/upgrade hosted clusters up to OCP 4.15.z.

MCE 2.6 can provision/upgrade hosted clusters up to OCP 4.16.z.

If you have MCE 2.4 (ACM 2.9) and see this hosted cluster upgrade dialog, that is wrong and we need to filter out 4.15.z from the new version selection list.

The supported version can be found in 

 oc get configmap -n hypershift supported-versions -o yam

apiVersion: v1
data:
  supported-versions: '{"versions":["4.14","4.13"]}'
kind: ConfigMap
metadata:
  creationTimestamp: "2024-04-03T18:31:55Z"
  labels:
    hypershift.openshift.io/supported-versions: "true"
  name: supported-versions
  namespace: hypershift
  resourceVersion: "16587589"
  uid: f0098422-a01f-4395-9385-e47e6f8c81be 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: