All posts
Kubernetes

EKS 1.31 Is Auto-Upgraded After November 26, 2026, and 1.34 Starts Costing Six Times More on December 2

By

November 2, 2026

5 min read

Kubernetes 1.31 on EKS reaches the end of extended support on November 26, 2026; after that AWS upgrades the control plane on its own schedule, with no notice and no rollback. Version 1.34 leaves standard support on December 2, when the control plane goes from $0.10 to $0.60 an hour. What happens, what doesn't, and what to do this month.

EKS
EKS Upgrades
Kubernetes
Extended Support
Deadlines

Version

End of standard support

End of extended support

What happens

1.31

November 26, 2025

November 26, 2026

Control plane auto-upgraded after this date, at a time AWS doesn't announce

1.32

March 23, 2026

March 23, 2027

On extended support now: $0.60 an hour

1.33

July 29, 2026

July 29, 2027

On extended support now: $0.60 an hour

1.34

December 2, 2026

December 2, 2027

Extended support billing starts December 2

From the EKS Kubernetes release calendar. Billing for extended support starts at 00:00 UTC on the end-of-standard-support date.

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.

What the automatic upgrade does, and doesn't

  • Only the control plane is upgraded. Managed node groups and self-managed nodes stay on the old version; Auto Mode nodes may update.

  • AWS gives no time and sends no notice before it happens, and an automatically upgraded cluster can't be rolled back.

  • Add-ons (VPC CNI, CoreDNS, kube-proxy) and anything using APIs removed in the new version are yours to fix afterwards.

  • Nodes keep working up to three minor versions behind the control plane, but that skew isn't a state to stay in.

The money

Standard support is $0.10 per cluster-hour, about $73 a month. Extended support is $0.60, about $438. Ten clusters left on 1.34 past December 2 cost an extra $3,650 a month for no new capability.

This month

  1. Run aws eks describe-cluster-versions and list every cluster's version in every account and Region.

  2. Upgrade any 1.31 cluster yourself before November 26, one minor version at a time, so you choose the time and can roll back within seven days.

  3. Schedule 1.34 clusters to 1.35 before December 2.

  4. Check EKS upgrade insights for deprecated APIs before each step.

  5. Upgrade node groups and add-ons right after each control plane step; restart Fargate pods so they pick up the new kubelet.

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 November 2, 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.