Reference Source

kube-apiserver and kube-apiserver (HA instances)

For kube-apiserver and kube-apiserver (HA instances), skew rule is the newest and oldest kube-apiserver instances must be within one minor version; max skew (minor versions) is 1; may the second component be newer? is symmetric - the page bounds the gap between the newest and oldest instance without naming a governed side; worked example is newest kube-apiserver is at 1.37 other kube-apiserver instances are supported at 1.37 and 1.36; newest release when captured is 1.37, recorded from its source on 2026-09-01; source re-checked 2026-09-16.

Component pair
kube-apiserver and kube-apiserver (HA instances) our reading
Skew rule
the newest and oldest kube-apiserver instances must be within one minor version verified
Max skew (minor versions)
1 our reading
May the second component be newer?
symmetric - the page bounds the gap between the newest and oldest instance without naming a governed side our reading
Worked example
newest kube-apiserver is at 1.37 other kube-apiserver instances are supported at 1.37 and 1.36 verified
Newest release when captured
1.37 verified
Upgrade prerequisite
In a single-instance cluster, the existing kube-apiserver instance is 1.36 In an HA cluster, all kube-apiserver instances are at 1.36 or 1.37 verified
Sourcekubernetes.io
Verified
Review by
DatasetKubernetes component version skew policy: how far apart component versions can be in a supported cluster

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

the newest and oldest kube-apiserver instances must be within one minor version.

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: newest kube-apiserver is at 1.37 other kube-apiserver instances are supported at 1.37 and 1.36

Newest release when captured

The Kubernetes project maintains release branches for the most recent three minor releases (1.37, 1.36, 1.35).

Upgrade prerequisite

Pre-requisites: In a single-instance cluster, the existing kube-apiserver instance is 1.36 In an HA cluster, all kube-apiserver instances are at 1.36 or 1.37 (this ensures maximum skew of 1 minor version between the oldest and newest kube-apiserver instance)

— all from kubernetes.io, retrieved 2026-09-01

Source

Last verified against source: . Due for re-check by . This page as Markdown · OKF bundle · full dataset as JSON.