Many teams don’t realize this until it shows up on the AWS bill.
Amazon EKS has two support modes for Kubernetes versions: standard support and extended support. The difference between them is not just lifecycle; it is cost.
Standard vs Extended Support
-
Standard support:
$0.10 per hourper cluster -
Extended support:
$0.60 per hourper cluster (6× more)
Extended support applies when a Kubernetes version goes out of standard support. At first, this increase may seem small, but if you manage multiple clusters across development, staging, and production, the cost adds up very quickly.
Kubernetes Version Lifecycle in EKS
Kubernetes releases a new minor version roughly every four months. AWS EKS follows this model and supports:
- The latest three minor versions under standard support
- About 14 months of standard support per version
- An additional ~12 months of extended support at a higher cost
Standard support versions receive newer security patches, API updates, and configuration improvements. Staying within these versions is strongly recommended.
What Happens If You Don’t Upgrade
AWS notifies customers through the AWS Personal Health Dashboard at least 60 days before a cluster enters extended support.
If a cluster goes beyond extended support:
- AWS will automatically upgrade the control plane
- You must manually upgrade worker nodes and add-ons such as CoreDNS, kube-proxy, VPC CNI, and CSI drivers
- Kubernetes version skew policies apply: upgrades must happen one minor version at a time, and worker nodes must not lag too far behind the control plane
Ignoring this can lead to broken workloads or cluster instability.
Conclusion
Keeping your EKS clusters within standard support is not just a security or stability best practice, it is a cost avoidance strategy. Planning upgrades early helps you avoid surprise bills and keeps your platform healthy.
Top comments (1)
Well said. This is easy cost savings for platform teams who rely on AWS EKS.
Thank you for sharing.