kube-apiserver and kube-proxy
For kube-apiserver and kube-proxy, skew rule is kube-proxy may be up to three minor versions older than kube-apiserver; max skew (minor versions) is 3; may the second component be newer? is no - kube-proxy must not be newer than kube-apiserver; exception for older versions is kube-proxy < 1.25 may only be up to two minor versions older than kube-apiserver; worked example is kube-apiserver is at 1.37 kube-proxy is supported at 1.37, 1.36, 1.35, and 1.34, recorded from its source on 2026-09-01; source re-checked 2026-09-16.
- Component pair
- kube-apiserver and kube-proxy our reading
- Skew rule
- kube-proxy may be up to three minor versions older than kube-apiserver verified
- Max skew (minor versions)
- 3 our reading
- May the second component be newer?
- no - kube-proxy must not be newer than kube-apiserver our reading
- Exception for older versions
- kube-proxy < 1.25 may only be up to two minor versions older than kube-apiserver verified
- Worked example
- kube-apiserver is at 1.37 kube-proxy is supported at 1.37, 1.36, 1.35, and 1.34 verified
- Newest release when captured
- 1.37 verified
- HA cluster caveat
- If version skew exists between kube-apiserver instances in an HA cluster, this narrows the allowed kube-proxy versions. verified
- Upgrade prerequisite
- The kube-apiserver instances kube-proxy communicates with are at 1.37 verified
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
What the source says
kube-proxy must not be newer than kube-apiserver. kube-proxy may be up to three minor versions older than kube-apiserver (kube-proxy < 1.25 may only be up to two minor versions older than kube-apiserver).
— kubernetes.io, retrieved 2026-09-01
Where each value comes from
This source states these in separate places, so each value is shown with the passage that states it.
Worked example
Example: kube-apiserver is at 1.37 kube-proxy is supported at 1.37, 1.36, 1.35, and 1.34
Newest release when captured
The Kubernetes project maintains release branches for the most recent three minor releases (1.37, 1.36, 1.35).
HA cluster caveat
Note: If version skew exists between kube-apiserver instances in an HA cluster, this narrows the allowed kube-proxy versions.
Upgrade prerequisite
kube-proxy Pre-requisites: The kube-apiserver instances kube-proxy communicates with are at 1.37
— all from kubernetes.io, retrieved 2026-09-01
Source
- kubernetes.iohttps://kubernetes.io/releases/version-skew-policy/