Skip to main content
This article explains how Kubernetes manages software releases, how to read Kubernetes version numbers, and where to find release artifacts and compatibility guidance.

Check the cluster version

When you install a Kubernetes cluster, each node runs a specific Kubernetes version. To see the version for each node, run:
Example output:
This shows the cluster is running v1.33.0.

Semantic versioning in Kubernetes

Kubernetes follows semantic versioning with three components: major, minor, and patch. Minor releases introduce capabilities and API changes; patch releases address bugs and security fixes to improve stability.
The image shows a software version label "v1.33.0" with pointers marking the major, minor, and patch components. Underneath, "Minor" lists Features and Functionalities while "Patch" notes Bug Fixes.

Release cadence and history

Kubernetes has maintained a steady release cadence since the first v1.0 release in July 2015. Minor versions are released regularly; for example, v1.20 shipped in December 2020 and v1.33 in April 2025. Approximate timeline of notable releases:
A vertical timeline on a dark blue background showing software release milestones with white dots and blue rounded date labels (e.g., Mar 2015 v0.12, June 2015 v0.20, Dec 2016 v1.5, March 2018 v1.10, Dec 2020 v1.20, April 2025 v1.33). The dates and version numbers are placed along a centered vertical line.

Alpha, Beta, and Stable (GA) stages

Before features reach general availability (GA), they typically progress through these stages:
  • Alpha: experimental and often disabled by default. Features may change or be removed.
  • Beta: more stable and usually enabled by default; behavior is well-tested.
  • Stable / GA: production-ready, supported, and unlikely to change in incompatible ways.
Release notes and GitHub releases list these pre-release stages for features and component changes. See the Kubernetes Releases page for changelogs and downloadable assets:
A screenshot of a webpage showing the Kubernetes "Release History" with version details for 1.33 and 1.32. A highlighted button below shows the GitHub URL "https://github.com/kubernetes/kubernetes/releases."

Release artifacts and component versioning

When you download an official Kubernetes release (for example, kubernetes.tar.gz) and extract it, the archive contains binaries built for that exact release version. Typical binaries include:
  • kube-apiserver
  • kube-controller-manager
  • kube-scheduler
  • kubelet
  • kube-proxy
  • kubectl
Some ecosystem components are versioned and released independently of the core Kubernetes version. Notable examples:
Before upgrading or installing a specific Kubernetes release, always check the release notes for supported etcd and CoreDNS versions to ensure component compatibility.
A stylized diagram of Kubernetes components showing colored blocks for kube-apiserver, controller-manager, kube-scheduler, kubelet, kube-proxy and kubectl, each labeled v1.XX.Y. Below are etcd Cluster (v3.2.18) and CoreDNS (v1.1.3) with a version icon at the top.

Further reading and references

Performing Kubernetes cluster upgrades is a separate, in-depth topic (planning, control-plane upgrade order, node upgrades, and rollback strategies) and is not covered in this article.

Watch Video