About Kubernetes’ version skew policy#
Kubernetes clusters’ software running on various machines is designed to work even when various components gets upgraded independently of each other - at least as long as the components don’t get too mismatched versions.
The tolerated mismatch of versions between k8s software components is called the supported version skew, and Kubernetes provides a version skew policy about this.
Practically for us when upgrading k8s clusters, we need to know that:
Highly available clusters’ control planes can only be upgraded one minor version at a time (
api-serverrequirement).All of our new clusters and most of our old clusters are highly available, so our documentation assumes we need to respect this constraint.
Nodes’ k8s version must not be newer than the control plane, and be at most three minor versions older (
kubeletrequirement).