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.
| Version | End of standard support | End of extended support |
|---|---|---|
| 1.31 | Nov 26, 2025 | Nov 26, 2026 |
| 1.32 | Mar 23, 2026 | Mar 23, 2027 |
| 1.33 | Jul 29, 2026 | Jul 29, 2027 |
| 1.34 | Dec 2, 2026 | Dec 2, 2027 |
| 1.35 | Mar 27, 2027 | Mar 27, 2028 |
| 1.36 | Aug 2, 2027 | Aug 2, 2028 |
| 1.37 | Dec 1, 2027 | Dec 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.
| Version | End of life (community support) | LTS end of life |
|---|---|---|
| 1.33 | Jul 2026 | Jul 2027 |
| 1.34 | Nov 2026 | Nov 2027 |
| 1.35 | Mar 2027 | Mar 2028 |
| 1.36 | Jun 2027 | Jun 2028 |
| 1.37 | Oct 2027 | Oct 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.
| Version | End of standard support | End of extended support |
|---|---|---|
| 1.33 | Aug 12, 2026 | Jun 12, 2027 |
| 1.34 | Jan 25, 2027 | Nov 25, 2027 |
| 1.35 | Apr 11, 2027 | Feb 11, 2028 |
| 1.36 | Aug 9, 2027 | Jun 9, 2028 |
| 1.37 | Dec 22, 2027 | Oct 22, 2028 |
How to stay ahead
- Inventory every cluster, its version, node pools and add-ons, across all clouds.
- Scan for deprecated APIs in manifests and Helm charts before each step.
- Upgrade one minor version at a time, control plane first, then node pools, ideally with blue/green node groups.
- Rehearse on a staging cluster that mirrors production add-ons.
- Make it routine. Three releases a year means upgrades should be a pipeline, not a project.
Sources
- AWS: Kubernetes version lifecycle on Amazon EKS
- Microsoft Learn: Supported Kubernetes versions in AKS
- Google Cloud: GKE release schedule
- Kubernetes: Releases and support period
Checked on November 15, 2026. Vendors can change dates and terms, so confirm against the source before you rely on them.


