Azure Linux 2.0 End of Life Announcement: Upgrade Required for AKS Arc Users

Important Update: End of Life for Azure Linux 2.0 and Transition to 3.0

Microsoft has issued an important warning regarding the impending end of support for Azure Linux 2.0, which is utilized in the Azure Kubernetes Service (AKS) through Azure Arc. The scheduled end of life (EOL) for this version is July 31, 2025. After this date, users will no longer receive updates, security patches, or any form of support for Azure Linux 2.0. Continuing to use this version post-EOL could leave systems increasingly exposed to vulnerabilities caused by the lack of maintenance.

Introducing Azure Linux 3.0

In response to these developments, Azure Linux 3.0 has been released, featuring substantial improvements across several key areas such as performance, security, and the overall developer experience. This new version includes an upgrade of the Linux kernel from 5.15 to 6.6, which enhances performance and compatibility with newer hardware. Additionally, the Containerd package is upgraded from version 1.6.26 to 1.7.13, which aids in improving container management efficiency.

Moreover, the SystemD package has been upgraded from version 250 to 255, significantly improving the management of systems and services. OpenSSL has also seen a noteworthy jump from version 1.1.1k to 3.3.0, heightening the encryption standards and security protocols available in this version. Azure Linux 3.0 not only features these upgrades but also introduces a broader array of packages and enhanced tools for developers.

Support Timeline and Upgrade Path

Typically, major versions of Azure Linux have a support lifespan of three years, positioning the EOL for Azure Linux 3.0 in the Summer of 2027. The new version became generally available in August 2024. Microsoft emphasizes the necessity for users to upgrade their Azure Local instances to the 2507 release—a prerequisite before migrating to Azure Linux 3.0.

Once you’ve successfully upgraded your Azure Local instance, the next step involves upgrading your Kubernetes clusters. Microsoft facilitates continuity by allowing users to maintain the same Kubernetes version during the upgrade process. This can be done by specifying the existing version number when executing the aksarc upgrade command.

Post-Upgrade Verification

After completing the upgrade, users can verify the kernel version on their Linux nodes using the following command, making sure to adjust the file path as necessary:

kubectl --kubeconfig /path/to/aks-cluster-kubeconfig get nodes -o wide

Completing this upgrade is essential for ongoing support from Microsoft. For more detailed information, including contact details for the AKS Arc team, please refer to Microsoft’s official announcement.

Source & Images