Time to Bail · Boarding pass
Act. You can stay.
AKS 1.34 reaches end of life on November 30, 2026. AKS plans to upgrade clusters still on it in June 2027.[1]
Act means: change a setting or plan before the date. You can stay.
AKS Kubernetes 1.34 end of life: November 2026
Kubernetes 1.34 on Azure Kubernetes Service reaches end of life in November 2026. After a 60-day grace period, AKS can upgrade clusters that still run it. This can happen outside your maintenance window.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
In the Azure portal, check the Kubernetes version of each cluster. Look for 1.34.
In the portal, open Diagnose and solve problems, then Kubernetes API deprecations.
Run az aks upgrade to a supported version, then set the stable auto-upgrade channel.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| End of life | November 2026, which AKS counts as November 30, 2026[1] |
|---|---|
| Version | Kubernetes 1.34 on AKS (not LTS)[1] |
| Grace period | 60 days after the end-of-life date to upgrade on your own terms[1] |
| Platform-initiated upgrade | Planned for June 2027 for clusters still on 1.34[1] |
| That upgrade | Does not follow your maintenance window or run the deprecated API check[2] |
| With LTS enabled | 1.34 is supported until November 2027[1] |
| LTS version also ending | Kubernetes 1.31 LTS ends November 2026; its platform upgrade is planned for June 2027[1] |
| Clusters on 1.34 | Out of support after November 30, 2026[1] |
Check it yourself. Every fact above links here.
Time to bail on AKS clusters on Kubernetes 1.34? Act. You can stay. AKS 1.34 reaches end of life on November 30, 2026. AKS plans to upgrade clusters still on it in June 2027.
On our scale this is Act: change a setting or plan before the date. You can stay.
Kubernetes 1.34 on Azure Kubernetes Service reaches end of life in November 2026. After a 60-day grace period, AKS can upgrade clusters that still run it. This can happen outside your maintenance window.
Here are the facts we checked:
You can stay on Azure Kubernetes Service (AKS). You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Microsoft is the main source for this page. Azure Kubernetes Service (AKS) has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Clusters on 1.34: Out of support after November 30, 2026.
The date to remember is November 2026, which AKS counts as November 30, 2026. Make the change before then.
A few tips:
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.
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.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on AKS clusters on Kubernetes 1.34 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.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.