version skew
How far apart the versions of cluster components, such as the API server, kubelets and kubectl, are allowed to be.
In more detail
The published policy lets kubelets be up to three minor versions older than the API server, but never newer, and kubectl one minor version either way. That is why you upgrade the control plane before workers and one minor version at a time. Check the policy for the release you run, because it has changed over time.
Related terms
- kubeadm — The official Kubernetes tool for creating and upgrading clusters, which runs the control plane as static pods.
- kubelet — The agent on every Kubernetes node that starts and watches the node's containers and reports back to the API server.
- kubectl — The command-line tool for talking to a Kubernetes cluster's API server: creating, reading, changing and deleting objects.
Taught in
- Upgrades In The Only Order That Works — Certified Kubernetes Administrator (CKA) Exam Prep
- Mock Exam: Seventeen Tasks Against The Clock — Certified Kubernetes Administrator (CKA) Exam Prep
- Bootstrap A Local Cluster And Check Your Context — Kubernetes: Production-Grade Container Orchestration
- Node Affinity, Pod Affinity And Topology Spread — Kubernetes: Production-Grade Container Orchestration
- kubeadm, High Availability And Cluster Lifecycle — Kubernetes: Production-Grade Container Orchestration
- Drain, Upgrade, Version Skew And Certificate Maintenance — Kubernetes: Production-Grade Container Orchestration