1. Proposed title of this feature request

RFE: Disable the desiredUpdate version verification in the ClusterCurator

2. What is the nature and description of the request?

When creating a ClusterCurator that would upgrade the cluster + update the channel it’s stuck. (no pods are created and in UI loops with channel change + prehook)
It seems that it cannot do the two things at the same time.

Originally, it is a limitation on the OCP side since they don't provide the availableUpdates until after the channel is updated. We are just pulling the availableUpdates data from the managed cluster ClusterVersion to the ManagedClusterInfo CR.

Proposed Feature:

By disabling the desiredUpdate version verification when a new channel is set, the upgrade would proceed.

The requirement would be that the user needs to know exactly the version they are using ie. whether it's a recommended version since we are not doing any verifications.

3. Why does the customer need this? (List the business requirements here)

The customer has automated the of managed clusters upgrade using the ClusterCurator but is not able to update the channel.