Skip to main content
BumbleTap
Add to ChromeInstall

Kubernetes End of Life (EOL) Dates: Every Version and Its Support Status

Release, maintenance mode and end-of-life dates for every Kubernetes minor version, and how the EKS, GKE and AKS windows differ from upstream.

Updated Dates checked Shahzeb Umer

Where to be now

Be on Kubernetes 1.37.

Supported now
3
Next to end
Kubernetes 1.3528 February 2027, in 101 days
Newest release
Kubernetes 1.37Released 26 August 2026
Why Kubernetes 1.37
It is the newest minor version, patched upstream until 28 October 2027, and it is already generally available on EKS (since 1 October 2026), AKS (October 2026) and GKE's Regular channel (since 22 October 2026).
  • Bug and security fixes
  • Security fixes only
  • Extended support, often paid
  • Today

Kubernetes: 3 of the 12 releases shown are supported today. 1.37 from 26 Aug 2026 to 28 Oct 2027; 1.36 from 22 Apr 2026 to 28 Jun 2027; 1.35 from 17 Dec 2025 to 28 Feb 2027; 1.34 from 27 Aug 2025 to 27 Oct 2026; 1.33 from 23 Apr 2025 to 28 Jun 2026; 1.32 from 11 Dec 2024 to 28 Feb 2026; 1.31 from 13 Aug 2024 to 11 Nov 2025; 1.30 from 17 Apr 2024 to 15 Jul 2025; 1.29 from 13 Dec 2023 to 28 Feb 2025; 1.28 from 15 Aug 2023 to 28 Oct 2024; 1.27 from 11 Apr 2023 to 28 Jun 2024; 1.26 from 8 Dec 2022 to 28 Feb 2024.

Version guides

Your version, in depth.1

Supported

Versions still getting fixes3

VersionReleasedBug fixes untilSecurity fixes untilLatest
1.371.37.227 Oct 2026
1.361.36.627 Oct 2026
1.35Kubernetes 1.35 end of life1.35.1027 Oct 2026

Ended

Versions that no longer get fixes19

VersionReleasedEndedFinal release
1.341.34.13
1.331.33.13
1.321.32.13
1.311.31.14
1.301.30.14
1.291.29.15
1.281.28.15
1.271.27.16
Show 11 older versions
1.261.26.15
1.251.25.16
1.241.24.17
1.231.23.17
1.221.22.17
1.211.21.14
1.201.20.15
1.191.19.16
1.181.18.20
1.171.17.17
1.161.16.15

Reading the dates

What Kubernetes’s own terms mean.

How long a release lasts
Kubernetes ships a new minor version about three times a year and maintains release branches for the three most recent. Each minor version gets about 14 months of patch releases: roughly 12 months of regular patches, then two months of maintenance mode limited to CVE fixes, dependency updates and critical core component fixes.
standard period
The first twelve months of a minor version's support, with patch releases carrying bug and security fixes, normally once a month.
maintenance mode
The last two months before end of life, starting on the 28th of a month, when release managers cut patches only for CVEs, dependency issues such as base image updates, and critical core component issues.
EOL (end of life)
Cherry-picks to the release branch close, and the version gets no more security updates or bug fixes from the project.

Worth knowing

Before you plan around these dates.

Upstream Kubernetes dates matter most if you build and run clusters yourself. On EKS, GKE or AKS, the date that forces an upgrade is your provider's, and the providers agree neither with upstream nor with each other. Upstream end dates usually fall on the 28th, a day the project chose because every month has one.

Take 1.34. The Kubernetes project ended it on 27 October 2026.

  • EKS: standard support until 2 December 2026, extended support until 2 December 2027.
  • GKE: standard support until 25 January 2027, extended support until 25 November 2027.
  • AKS: community support until November 2026, Long Term Support until November 2027.

After the upstream end of life, each provider keeps shipping security patches for the versions it still supports.

What the extra time costs

EKS charges $0.60 per cluster per hour in extended support, against $0.10 in standard support, and extended support is on by default. GKE charges pay-per-use costs while a cluster on its Extended channel is in the extended support period. AKS Long Term Support requires moving the cluster to the Premium tier.

What happens at the end

When a provider's window closes, it upgrades the cluster for you, on its own schedule. EKS gives no notice of the exact time, and its automatic upgrade covers only the control plane: managed node groups and self-managed nodes stay on the old version. The Kubernetes project tests a control plane with nodes up to three minor versions older, so nodes within that range keep working after the jump, though EKS recommends keeping nodes and control plane on the same version. AKS begins platform-initiated upgrades on 1 June 2027, and those upgrades can override a Pod Disruption Budget that blocks a node drain.

Common questions

Which Kubernetes versions are still supported?
1.35, 1.36 and 1.37. Upstream support ends on 28 February 2027 for 1.35, 28 June 2027 for 1.36 and 28 October 2027 for 1.37. Kubernetes 1.34 reached end of life on 27 October 2026.
How long is a Kubernetes version supported?
About 14 months upstream: roughly 12 months of regular patch releases, then 2 months of maintenance mode. Managed services run longer. EKS, for example, gives 14 months of standard support from its own release date plus 12 months of paid extended support, 26 months in all.
How often does Kubernetes release a new version?
About three times a year. 1.35 came out on 17 December 2025, 1.36 on 22 April 2026 and 1.37 on 26 August 2026. The 1.38 release team has scheduled 1.38.0 for 16 December 2026.
When does Kubernetes 1.35 reach end of life?
Upstream on 28 February 2027, after entering maintenance mode on 28 December 2026. On EKS, standard support runs to 27 March 2027 and extended support to 27 March 2028. GKE ends standard support on 11 April 2027, and AKS ends community support in March 2027. Kubernetes 1.35 end of life covers each of them.
Do EKS, GKE and AKS follow the upstream Kubernetes dates?
No. Each runs its own calendar, usually ending later than upstream, with a paid way to stay longer. EKS gives 14 months of standard support and 12 months of extended support at $0.60 per cluster per hour instead of $0.10. GKE gives 14 months of standard support, and its Extended channel keeps a version for up to 24 months, with pay-per-use costs in the extended period. AKS gives 12 months of community support, and Long Term Support on the Premium tier adds a second year.
What happens when a managed cluster's version runs out of support?
The provider upgrades it. EKS automatically upgrades the control plane at any time after the end of extended support, without notice, and leaves managed node groups and self-managed nodes on the old version. GKE auto-upgrades clusters whose minor version has reached end of support. AKS starts platform-initiated upgrades on 1 June 2027 for clusters still on an unsupported version after a 60-day grace period, and those upgrades do not follow your maintenance window.

Feeds and badge

Get told before the next Kubernetes version ends.

Calendar address

https://bumbletap.com/eol/calendar/kubernetes.ics

Open in your calendar appAdd to Google CalendarEvery product in one feed

README badge for Kubernetes 1.37

[![Kubernetes 1.37 end of life](https://img.shields.io/endpoint?url=https%3A%2F%2Fbumbletap.com%2Feol%2Fbadge%2Fkubernetes-1-37.json)](https://bumbletap.com/eol/kubernetes)

Rendered by shields.io from a small JSON file rebuilt daily. Swap the version in the address for any other line. It turns yellow 90 days out and red once support ends.

Sources

Where these dates come from.

Also on the calendar

End-of-life dates for the rest of your stack.