What changed
Time to bail on Amazon EKS clusters on Kubernetes 1.32? Act. You can stay. EKS 1.32 extended support ends March 23, 2027. Then AWS upgrades the control plane, with no rollback.
On our scale this is Act: change a setting or plan before the date. You can stay.
Extended support for Kubernetes 1.32 on Amazon EKS ends on March 23, 2027. After that, AWS upgrades the control plane with no notice, and it cannot be rolled back. Extended support costs more per hour.
Here are the facts we checked:
- End of extended support: March 23, 2027 (Amazon Web Services)
- Version: Kubernetes 1.32 on Amazon EKS (Amazon Web Services)
- If you do nothing: Auto-upgraded at any time after that date, with no notice before (Amazon Web Services)
- Can you roll back?: No. Clusters upgraded at the end of extended support cannot be rolled back (Amazon Web Services)
- What gets upgraded: Only the Kubernetes control plane (Amazon Web Services)
- New clusters: You can no longer create clusters on 1.32 after that date (Amazon Web Services)
- Price per cluster: $0.10 per hour in standard support; $0.60 per hour in extended support (Amazon Web Services)
- Next date: Kubernetes 1.33 extended support ends July 29, 2027 (Amazon Web Services)
- Clusters still on 1.32: Upgraded by AWS after March 23, 2027 (Amazon Web Services)
You can stay on Amazon EKS. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Amazon Web Services is the main source for this page. Amazon EKS has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Who is affected
Clusters still on 1.32: Upgraded by AWS after March 23, 2027.
The date to remember is March 23, 2027. Make the change before then.
What to do before March 23
- Check cluster versions. In the EKS console, look at the Kubernetes version of each cluster. Note any on 1.32.
- Upgrade on your own schedule. Upgrade the control plane, then node groups and add-ons. Test your apps after each step.
- Update nodes after any upgrade. AWS does not upgrade managed node groups or self-managed nodes for you.
A few tips:
- Make the change yourself before the date. Do not wait for the last reminder email.
- Write down your current plan or settings first, so you can compare after the change.
- After the change, open your settings again and check that it worked.
How to tell your users
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Options people mention
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
Questions people ask
No questions collected yet.
Sources