When no release image is provided on a HostedCluster, the backend hypershift operator picks the latest OCP release image within the operator's support windown.

Today this fails due to how the operator selects this default image. For example, hypershift operator 4.14 does not support 4.15, but the 4.15.0.rc.3 is picked as a default release image today. 

This is a result of not anticipating that release candidates would not be reported as the latest stable release. The filter used to pick the latest release needs to consider patch level releases before the next y stream release.

4.14    

100%    

    1.create a self managed hcp cluster and do not specify a release image
    

    the hcp will be rejected because the default release image picked does not fall within the support window

    hcp should be created with the latest release image in the support window