Upgrade your AKS clusters to Kubernetes version 1.31 or later

Susai Alphonse 21 Reputation points Microsoft External Staff
2025-07-29T16:31:53.7966667+00:00

Hello Team,

one of my customers mentioned about the short notice for the AKS retirement notification, which left little time for teams to react. And also moving forward wow to get the early notifications so that we have sufficient time to take actions.

User's image

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
0 comments No comments
{count} votes

Accepted answer
  1. Nikhil Duserla 8,515 Reputation points Microsoft External Staff Moderator
    2025-07-29T17:23:54.11+00:00

    Hello @Susai Alphonse ,

    Establishing a proactive communication strategy with your customers around service retirements such as Azure Kubernetes Service (AKS) is crucial to minimizing disruption and avoiding surprises.

    To support this, Microsoft provides the AKS Communication Manager, a tool designed to streamline notifications related to AKS maintenance events and planned upgrades. The Azure Kubernetes Service (AKS) Communication Manager streamlines notifications for all your AKS maintenance tasks by using Azure Resource Notifications and Azure Resource Graph frameworks. This tool enables you to closely monitor your upgrades because it provides you with timely alerts on event triggers and outcomes. If maintenance fails, it notifies you with the reasons for the failure, reducing operational hassles related to observability and follow-ups.

    You can learn how to set it up by visiting: https://learn.microsoft.com/en-us/azure/aks/aks-communication-manager

    If you have any further queries, do let us know.


1 additional answer

Sort by: Most helpful
  1. Marco Cruz 0 Reputation points Microsoft Employee
    2025-08-04T09:51:25.7466667+00:00

    Hello @Susai Alphonse ,

    I hope you are doing well.

    Following discussions with our AKS Product teams we’ve identified that the communication regarding the end-of-life (EOL) for Kubernetes version 1.30 was not delivered as expected. This was a general issue that affected multiple customers, including the customer you reported.

    To address this our team has decided to extend the EOL period by three weeks. The deprecation process will now begin no later than August 22.

    The AKS release calendar was updated to reflect this change.

    This extension period now provides ample time for Customers to prepare to smoothly upgrade to version 1.31 or switch to the 1.30 LTS version.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.