Kubernetes
Server AppKubernetes 1.37 is the newest actively maintained release, currently at patch 1.37.0. 4 of 22 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 1.34, on October 27, 2026.
Support pattern
How Kubernetes has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.
Support windows have stayed consistent across the tracked history, so past cycles are a reasonable guide to what a new one will get.
Computed from release and end-of-life dates tracked for Kubernetes. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.
How Kubernetes versioning, EOL & security support work
Kubernetes ships new minor releases (1.X) on a regular cadence managed by its Release Team, and only a small, rolling set of the most recent minor versions is covered by official support at any given time. Within a supported minor version, patch releases are cut on a roughly monthly cadence, faster right after a new minor ships, and critical fixes can trigger an out-of-cycle release.
Kubernetes runs a coordinated disclosure process through its Security Response Committee: reports go through its bug bounty program or privately to [email protected], and a public disclosure date is negotiated with the reporter. Fixes are shipped as patch releases to in-support branches; a version that has already reached end of life sits outside this process, so it will not receive a fix even for a newly disclosed vulnerability.
Sources: Kubernetes Patch Releases policy, Kubernetes security vulnerability disclosure process
Release lifecycle
Get an email when Kubernetes ships a release, announces an end-of-life date, or moves a date it already announced.
Get Kubernetes alerts