timetobail
My stack

Amazon EKS · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Amazon EKS clusters on Kubernetes 1.31?

Time to Bail · Boarding pass

FromAmazon EKS clusters on Kubernetes 1.31
ToYour pick

Act. You can stay.

EKS 1.31 extended support ends November 26, 2026. Then AWS upgrades the control plane, with no rollback.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
End of extended support
Time left
41days
Status
Act

Amazon EKS 1.31 extended support ends November 26, 2026

Extended support for Kubernetes 1.31 on Amazon EKS ends on November 26, 2026. After that, AWS upgrades the control plane with no notice, and it cannot be rolled back. Extended support costs more per hour.

What to do before November 26

Tick steps as you go. Your progress stays in this browser.

  1. Check cluster versions

    In the EKS console, look at the Kubernetes version of each cluster. Note any on 1.31 to 1.34.

  2. Upgrade on your own schedule

    Upgrade the control plane, then node groups and add-ons. Test your apps after each step.

  3. Watch the next dates

    Kubernetes 1.34 leaves standard support on December 2, 2026. Then it costs the higher hourly price.

Facts we checked

Facts and their sources
End of extended supportNovember 26, 2026[1]
VersionKubernetes 1.31 on Amazon EKS[1]
If you do nothingAuto-upgraded at any time after that date, with no notice before[1]
Can you roll back?No. Clusters upgraded at the end of extended support cannot be rolled back[1]
What gets upgradedOnly the Kubernetes control plane[1]
Price per cluster$0.10 per hour in standard support; $0.60 per hour in extended support[2]
Upgrade policyEXTENDED by default for new and existing clusters[1]
Next dateKubernetes 1.34 standard support ends December 2, 2026[1]
Clusters still on 1.31Upgraded by AWS after November 26, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Understand the Kubernetes version lifecycle on EKS Amazon Web Services · primary · checked Oct 13
  2. Amazon EKS pricing Amazon Web Services · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Amazon EKS clusters on Kubernetes 1.31? Act. You can stay. EKS 1.31 extended support ends November 26, 2026. 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.31 on Amazon EKS ends on November 26, 2026. 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: November 26, 2026 (Amazon Web Services)
  • Version: Kubernetes 1.31 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)
  • Price per cluster: $0.10 per hour in standard support; $0.60 per hour in extended support (Amazon Web Services)
  • Upgrade policy: EXTENDED by default for new and existing clusters (Amazon Web Services)
  • Next date: Kubernetes 1.34 standard support ends December 2, 2026 (Amazon Web Services)
  • Clusters still on 1.31: Upgraded by AWS after November 26, 2026 (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.31: Upgraded by AWS after November 26, 2026.

The date to remember is November 26, 2026. Make the change before then.

What to do before November 26

  1. Check cluster versions. In the EKS console, look at the Kubernetes version of each cluster. Note any on 1.31 to 1.34.
  2. Upgrade on your own schedule. Upgrade the control plane, then node groups and add-ons. Test your apps after each step.
  3. Watch the next dates. Kubernetes 1.34 leaves standard support on December 2, 2026. Then it costs the higher hourly price.

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

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Amazon EKS clusters on Kubernetes 1.31 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product