Azure Kubernetes Service End of Life Dates

other

Developers working with cloud-based applications and services often rely on robust platforms to manage, access, and develop their projects. Microsoft Azure, a cloud computing platform developed by Microsoft, has been a popular choice since its inception. Originally known as Windows Azure, this platform has undergone significant transformations over the years, offering a wide range of tools and services to individuals, companies, and governments. The Azure Kubernetes Service, a key component of the Azure ecosystem, enables developers to deploy, manage, and scale containerized applications with ease. Maintained by Microsoft, this service has gained popularity among developers due to its flexibility, security, and scalability.

The end-of-life landscape for Azure Kubernetes Service is complex, with a total of 15 versions, out of which 12 have already reached their end-of-life. Currently, only 3 versions remain active, with the next version, 1.33, scheduled to expire on June 30, 2026. The most recent version to reach its end-of-life was 1.32, which expired on March 31, 2026. This frequent turnover of versions underscores the importance of staying up-to-date with the latest releases to ensure uninterrupted service and support. By keeping track of these version updates, developers can plan their application deployments and migrations accordingly, minimizing potential downtime and security risks.

From a security perspective, the Azure Kubernetes Service has a clean track record, with no known Common Vulnerabilities and Exposures (CVEs) reported to date. This means that there are no critical vulnerabilities that developers need to worry about, and no specific version is more affected than others. As a result, developers can focus on deploying and managing their applications without the added concern of addressing security flaws. However, it is still essential for developers to stay vigilant and monitor the service for any potential security issues that may arise in the future, ensuring the continued security and integrity of their applications and services.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
1.36 Jun 30, 2026Jun 30, 2027in 341dActive
1.35 Mar 5, 2026Mar 31, 2027in 250dActive
1.34 Jan 4, 2026Nov 30, 2026in 129dActive
1.33 Jun 17, 2025Jul 31, 2026in 7dEOL soon
1.32 Apr 6, 2025Mar 31, 2026115d agoEOL
1.31 Oct 25, 2024Nov 1, 2025265d agoEOL
1.30 Aug 5, 2024Aug 22, 2025336d agoEOL
1.29 Mar 18, 2024Mar 31, 2025480d agoEOL
1.28 Nov 7, 2023Jan 31, 2025539d agoEOL
1.27 Aug 16, 2023Jul 31, 2024723d agoEOL
1.26 Apr 18, 2023Apr 11, 2024834d agoEOL
1.25 Dec 14, 2022Jan 14, 2024922d agoEOL
1.24 Aug 17, 2022Jul 31, 20231089d agoEOL
1.23 Apr 26, 2022Apr 2, 20231209d agoEOL
1.22 Jan 10, 2022Dec 4, 20221328d agoEOL
1.21 Aug 18, 2021Jul 31, 20221454d agoEOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions