← sources

EKS 1.31 extended support ends Nov 26, then AWS auto-upgrades the control plane. 1.34 standard support ends Dec 2

source: reddit (reddit:kubernetes)published 2026-11-17 17:54ingested 2026-11-18 02:41

retained text

Disclosure: I'm the founder of Expiry Radar, a commercial tool that tracks dates like these. Everything below works only with aws cli.



Two EKS dates coming up:



\- 1.31: extended support ends Nov 26, 2026. After that AWS upgrades the control plane to the next version on its own schedule, so add-ons and node groups that aren't ready can break.

\- 1.34: standard support ends Dec 2, 2026. From then on the cluster bills extended support, $0.60 per cluster-hour instead of $0.10 (about $365/month more per cluster).



Check your clusters and what blocks the upgrade (per region):



for c in $(aws eks list-clusters --query 'clusters\[\]' --output text); do echo "$c $(aws eks describe-cluster --name "$c" --query cluster.version --output text)"; done

aws eks list-insights --cluster-name <name>

aws eks describe-cluster-versions --query 'clusterVersions\[\].\[clusterVersion,endOfStandardSupportDate,endOfExtendedSupportDate\]' --output table



\`list-insights\` is the useful one: it lists deprecated APIs still in use and add-on or node version skew before you upgrade.



Source for the dates: [https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html)



How are you handling upgrade from 1.31 to 1.32, in place or blue/green clusters?

document fetched 2026-11-18 00:41 · canonical https://reddit.com/r/kubernetes/comments/1xyr8mj/eks_131_extended_support_ends_nov_26_then_aws