Longstanding Kube API server operator code that enforces OpenShift's kubelet/KAS skew policy assumes that even-numbered minor releases are EUS releases, which support up to two minor releases of skew between kubelet versions and KAS versions. My understanding is that EUS policy and kubelet skew policy may both change in OCP 5. This Epic is about pinning down the details of the new policy, and then teaching the 4.22 Kube API server operator about the new policy, so that it is properly enforced for 4.22-to-5.0 updates. Ideally we can select a policy with enough confidence that the new policy implementation will also work for 4.23-to-whatever and 5.0-to-5.1, etc. But the minimum bar is just to get the 4.22-to-whatever policy figured out so we can get enforcing code landed to deliver that policy. I'm linking OTA-1785 as related, because it is also dependent on figuring out policy around things like "will 5.0 be EUS?".