• OCP is always subscribed to the stable channel initially, and often times a version on the fast channel is not part of the stable channel, which leads to the user seeing an error in the OCP console
• A Hive user should be able to specify which update channel a new cluster should use, because this cannot be determined from the version alone

As discussed in slack:
https://coreos.slack.com/archives/CE3ETN3J8/p1638454055159400

One suggested implementation approach: As hive use clusterimageset to specify the ocp release, it’s better to define the channel in clusterimageset and could tranfer it to desired ocp cluster.