All posts
Kubernetes

EKS Release Calendar 2026–2027: Every Version's End of Standard and Extended Support

By

October 25, 2026

6 min read

Kubernetes 1.31 clusters are auto-upgraded after November 26, 2026; 1.34 leaves standard support on December 2. Every EKS date from now to the end of 2027, what happens on each, and an upgrade routine that fits in a sprint.

EKS
Kubernetes
Upgrades
Extended Support
2027

How the calendar works

Each Kubernetes minor version gets 14 months of standard support on EKS from its EKS release, then 12 months of extended support at $0.60 per cluster-hour instead of $0.10. At the end of extended support EKS upgrades the control plane automatically, at a time it does not announce, and only the control plane: managed node groups and self-managed nodes stay where they were, and add-ons are yours to update.

Version

End of standard support

End of extended support

1.31

November 26, 2025

November 26, 2026 — auto-upgrades follow

1.32

March 23, 2026

March 23, 2027

1.33

July 29, 2026

July 29, 2027

1.34

December 2, 2026

December 2, 2027

1.35

March 27, 2027

March 27, 2028

1.36

August 2, 2027

August 2, 2028

1.37

December 1, 2027

December 1, 2028

From the Amazon EKS Kubernetes release calendar, October 2026. Billing for extended support starts at the beginning of the day standard support ends, UTC.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

An upgrade routine that fits in a sprint

  1. Check removed and deprecated APIs for the target version against what is deployed — EKS upgrade insights flags them per cluster.

  2. Update add-ons and Helm charts to versions that support the target, in a non-production cluster first.

  3. Upgrade the control plane. EKS lets you roll back within seven days of an in-place upgrade if something you missed breaks.

  4. Roll nodes: Auto Mode updates its own; managed node groups and self-managed nodes need an explicit update; Fargate pods need a restart to pick up the new kubelet.

  5. Repeat every four months, one version at a time. Skipping a cycle is how teams end up two versions behind and in extended support.

aws eks describe-cluster-versions returns every version's support dates, which makes a scheduled check — open a ticket ninety days before any cluster's end of standard support — about twenty lines of code.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.