As discussed this is the trickiest use case (some details in https://docs.google.com/document/d/1Eow2IReNWqnIh5HvCfcKV2MWgHUmFKSnBkt2rH6_V_M/edit)

This involves control plane and worker node skew. OCP aligns with kuberentes and allows a 2 version skew between them. The master version must match the OCP version but the non-master pools may lag behind. This means that we will need to accept more than 1 Customer Base Image with a compatible RHCOS version for users who have lagging non-master pools.

Let's spend a bit of time walking through this to inform our checks and design as it requires a bit of coordination and checks.