Kubernetes Release and Deprecation Calendar: Versions and EOL

This page tracks which Kubernetes versions still get patches: the upstream minor releases with their latest patch and end of life dates, how long Amazon EKS, Google GKE and Azure AKS support each one, and the removals and deprecations that need work before an upgrade. I keep it for platform and operations engineers who plan upgrades, and for anyone who needs a date they can cite. Every row links to the primary page I read it from. Last checked: 12 November 2026.

Latest changes

• 12 Nov 2026: First version of this page. The November patch round was targeted for 10 November, but the upstream stable-1.37 marker still pointed at v1.37.2 when I checked, so the October patches remain the latest (source).
• 10 Nov 2026: Google updated the GKE release schedule. It gives 11 November as the approximate start of auto-upgrades to 1.37 in the Rapid channel and to 1.36 in the Regular channel (source).
• 6 Nov 2026: v1.38.0-beta.0 was published, the first beta of the next minor release (source).
• 31 Oct 2026: The date from which AKS removes Azure Linux 2.0 node images, after which node pools still on them cannot scale (source).
• 28 Oct 2026: Patch releases 1.37.2, 1.36.6, 1.35.10 and 1.34.13 were published on GitHub (source).
• 27 Oct 2026: Kubernetes 1.34 reached upstream end of life (source). I covered what that means in Kubernetes 1.37 and 1.38: what's new in 2026.
• 6 Oct 2026: The Kubernetes blog published its guide to the cgroup v2 shift and the deprecation of cgroup v1 (source).
• 1 Oct 2026: Amazon EKS released Kubernetes 1.37 (source). My EKS upgrade guide walks through the move from 1.36.
• 30 Sep 2026: containerd 1.7 reached end of life in the containerd support table (source).
• 26 Aug 2026: Kubernetes 1.37 was released (source).

Upstream Kubernetes versions and end of life dates

The project maintains release branches for the three most recent minor versions, which today are 1.37, 1.36 and 1.35. I keep 1.34 in the table because it only just dropped off and the managed services still run it.

Two notes on reading this. Patch dates are the dates the GitHub releases were published, in UTC. And kubernetes.io/releases still showed the September patches (1.37.1, 1.36.5, 1.35.9, 1.34.12) as the latest when I checked, because its schedule data had not caught up with the October tags. When the site and the tags disagree, I go by the tags.

Managed service support: EKS, GKE and AKS

These are standard support windows, before any extended or long-term support option. EKS and GKE publish exact dates. AKS publishes months, and its docs say a month with no day means the last day of that month. GKE calls its dates best-effort predictions, so treat the future ones as likely to move by days.

The pattern worth noticing: for 1.34, every provider outlasts upstream. The version reached community end of life on 27 October 2026, yet it stays in standard support on all three for weeks or months longer. EKS, for one, says it backports applicable security patches to every version it still supports. The pricing and policy differences behind these windows are in my EKS vs GKE vs AKS comparison.

Upstream removals and deprecations that need action

Sorted by the version where the change first bites. "Removed" means the old path is gone in that version. "Deprecated" means it still works and you have until the stated version.

One row carries a caveat. The October cgroup v2 blog says the cgroup v1 fallback is "scheduled for removal in Kubernetes v1.38", while the 1.37 release blog only says a future release, and I found no cgroup v1 removal entry in the 1.38 changelog up to beta.0. I have left the row at "a future release" until the 1.38 notes settle it. The Ingress NGINX story, including what to move to, is in Ingress NGINX is retired: what replaces it.

Managed service deadlines

Dates where a provider does something to your cluster, or starts charging for it, whether or not you act.

How this page is maintained

I check it whenever a Kubernetes patch round, a minor release or a provider calendar update lands, and I change the "Last checked" date each time. Rows come only from primary sources: kubernetes.io, the kubernetes and sig-release repositories on GitHub, the containerd release table, and the AWS, Google and Microsoft documentation pages linked in each row. I deliberately leave out pricing, feature lists, distributions such as OpenShift and Rancher, and anything I could only find in a third-party summary. A row that I cannot confirm against its source gets removed, not guessed. Corrections are welcome at hello@ajayk.sh.

FAQ

What is the latest Kubernetes version in November 2026?

Kubernetes 1.37 is the latest minor release and 1.37.2, published on 28 October 2026, is its latest patch. The supported upstream versions are 1.37, 1.36 and 1.35. Kubernetes 1.38 is planned for 16 December 2026 and is in beta.

How long is a Kubernetes version supported?

Upstream supports each minor version for roughly 14 months: 12 months of standard patching, then two months of maintenance mode before end of life. Managed services run their own clocks. EKS gives 14 months of standard support from its own release date plus 12 months of paid extended support, AKS follows a 12-month policy with optional long-term support, and GKE publishes a per-version end of standard support date.

Is Kubernetes 1.34 still supported?

Not upstream: 1.34 reached end of life on 27 October 2026. It is still in standard support on EKS until 2 December 2026, on GKE until 25 January 2027 and on AKS until the end of November 2026. If you run it on self-managed clusters, plan the move to 1.35 or later now, one minor version at a time.

Related: Kubernetes 1.37 and 1.38: What's New in 2026 and What Got Removed, EKS vs GKE vs AKS in 2026: Same $0.10 Fee, Very Different Clusters and Ingress NGINX Is Retired: What Replaces It and How to Choose in 2026.