timetobail
My stack

Azure Kubernetes Service (AKS) · Forced move · Tracked since October 17, 2026 · Sources checked Oct 17

Time to bail on AKS clusters on Kubernetes 1.35?

Time to Bail · Boarding pass

FromAKS clusters on Kubernetes 1.35
ToYour pick

Act. You can stay.

AKS 1.35 reaches end of life on March 31, 2027. 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.

Gate closes
End of life
Time left
164days
Status
Act

AKS Kubernetes 1.35 end of life: March 2027

Kubernetes 1.35 on Azure Kubernetes Service reaches end of life in March 2027. After a 60-day grace period, AKS can upgrade clusters still on it, outside your maintenance window.

Email me 7 days before Mar 31

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

What to do before March 31

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

  1. Check cluster versions

    In the Azure portal, check the Kubernetes version of each cluster. Look for 1.35.

  2. Remove deprecated APIs

    In the portal, open Diagnose and solve problems, then Kubernetes API deprecations.

  3. Upgrade before the date

    Run az aks upgrade to a supported version, then set the stable auto-upgrade channel.

Email me 7 days before Mar 31

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
End of lifeMarch 2027, which AKS counts as March 31, 2027[1]
VersionKubernetes 1.35 on AKS (not LTS)[1]
Grace period60 days after the end-of-life date to upgrade on your own terms[1]
Platform-initiated upgradePlanned for June 2027 for clusters still on 1.35[1]
That upgradeDoes not follow your maintenance window or run the deprecated API check[2]
With LTS enabled1.35 is supported until March 2028[1]
LTS version also endingKubernetes 1.32 LTS ends March 2027; its platform upgrade is planned for June 2027[1]
Clusters on 1.35Out of support after March 31, 2027[1]

Sources

Check it yourself. Every fact above links here.

  1. Supported Kubernetes versions in Azure Kubernetes Service (AKS) Microsoft · primary · checked Oct 17
  2. Platform-initiated upgrades in Azure Kubernetes Service (AKS) Microsoft · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on AKS clusters on Kubernetes 1.35? Act. You can stay. AKS 1.35 reaches end of life on March 31, 2027. 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.35 on Azure Kubernetes Service reaches end of life in March 2027. After a 60-day grace period, AKS can upgrade clusters still on it, outside your maintenance window.

Here are the facts we checked:

  • End of life: March 2027, which AKS counts as March 31, 2027 (Microsoft)
  • Version: Kubernetes 1.35 on AKS (not LTS) (Microsoft)
  • Grace period: 60 days after the end-of-life date to upgrade on your own terms (Microsoft)
  • Platform-initiated upgrade: Planned for June 2027 for clusters still on 1.35 (Microsoft)
  • That upgrade: Does not follow your maintenance window or run the deprecated API check (Microsoft)
  • With LTS enabled: 1.35 is supported until March 2028 (Microsoft)
  • LTS version also ending: Kubernetes 1.32 LTS ends March 2027; its platform upgrade is planned for June 2027 (Microsoft)
  • Clusters on 1.35: Out of support after March 31, 2027 (Microsoft)

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.

Who is affected

Clusters on 1.35: Out of support after March 31, 2027.

The date to remember is March 2027, which AKS counts as March 31, 2027. Make the change before then.

What to do before March 2027, which AKS counts as March 31

  1. Check cluster versions. In the Azure portal, check the Kubernetes version of each cluster. Look for 1.35.
  2. Remove deprecated APIs. In the portal, open Diagnose and solve problems, then Kubernetes API deprecations.
  3. Upgrade before the date. Run az aks upgrade to a supported version, then set the stable auto-upgrade channel.

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 AKS clusters on Kubernetes 1.35 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