In Managed HyperShift products, like ARO/ROSA HCP, it would be useful if the product did not have to consider patch version skew within the same minor version between the control plane and nodepools. That is, currently this is allowed:

• 4.14.5 Control Plane
• 4.14.[0-5] NodePool

but we would like to also allow this scenario to be supported:

• 4.14.5 Control Plane
• 4.14.6+ NodePool

Use Cases:

Since these managed HyperShift products manage the control plane version for the customer, it would be nice if we can allow customers to upgrade their NodePools when OCP releases a new NodePool version and not have to depend on rollout/rollback processes that the managed products would do. From a kubelet/kube-apiserver perspective, this is generally supposed to work within a minor version, but would introduce a larger testing radius for OCP HyperShift.