Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Cloud & Platform

Kubernetes end-of-support calendar for EKS, AKS and GKE (2026–2028)

Managed Kubernetes retires a version every few months, and each provider handles the end differently: extended-support billing, platform support or forced upgrades. The dates, side by side.

By the SRASH team · · 6 min read

Key facts

  • Upstream Kubernetes ships a minor version roughly every four months and supports about the latest three.
  • On Amazon EKS, 1.31 leaves extended support on Nov 26, 2026 and 1.34 leaves standard support on Dec 2, 2026.
  • On AKS, 1.34 reaches end of life in November 2026; from June 2027 AKS upgrades clusters left on unsupported versions.
  • On GKE, 1.34 ends standard support on Jan 25, 2027.

Why this calendar matters

Kubernetes moves fast. The upstream project releases a new minor version roughly every four months, and each managed service then supports a version for a fixed window. Miss the window and one of three things happens: you pay more, you lose support, or the provider upgrades the cluster for you on its own schedule, deprecated APIs and all.

Amazon EKS

AWS gives each version 14 months of standard support, then 12 months of extended support billed per cluster-hour. When extended support ends, AWS auto-upgrades remaining clusters to the oldest version still in extended support.

VersionEnd of standard supportEnd of extended support
1.31Nov 26, 2025Nov 26, 2026
1.32Mar 23, 2026Mar 23, 2027
1.33Jul 29, 2026Jul 29, 2027
1.34Dec 2, 2026Dec 2, 2027
1.35Mar 27, 2027Mar 27, 2028
1.36Aug 2, 2027Aug 2, 2028
1.37Dec 1, 2027Dec 1, 2028

Azure Kubernetes Service (AKS)

AKS supports three generally available minor versions for about 12 months each, then gives a 60-day platform support grace period. Microsoft states that starting June 1, 2027, AKS automatically upgrades clusters that stay on an unsupported version after that grace period, and that this upgrade does not follow your maintenance window or stop for deprecated API usage. Long-term support (LTS) adds a second year if you enable it.

VersionEnd of life (community support)LTS end of life
1.33Jul 2026Jul 2027
1.34Nov 2026Nov 2027
1.35Mar 2027Mar 2028
1.36Jun 2027Jun 2028
1.37Oct 2027Oct 2028

Microsoft notes that where only a month is given, end of life is the last day of that month.

Google Kubernetes Engine (GKE)

GKE auto-upgrades clusters in release channels, and patches remain available until the end of standard support; the Extended channel keeps a version until the end of extended support. Google describes the dates as best-effort predictions.

VersionEnd of standard supportEnd of extended support
1.33Aug 12, 2026Jun 12, 2027
1.34Jan 25, 2027Nov 25, 2027
1.35Apr 11, 2027Feb 11, 2028
1.36Aug 9, 2027Jun 9, 2028
1.37Dec 22, 2027Oct 22, 2028

How to stay ahead

  1. Inventory every cluster, its version, node pools and add-ons, across all clouds.
  2. Scan for deprecated APIs in manifests and Helm charts before each step.
  3. Upgrade one minor version at a time, control plane first, then node pools, ideally with blue/green node groups.
  4. Rehearse on a staging cluster that mirrors production add-ons.
  5. Make it routine. Three releases a year means upgrades should be a pipeline, not a project.

Sources

Checked on November 15, 2026. Vendors can change dates and terms, so confirm against the source before you rely on them.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.