← ← Back to all products
All badges & lifecycle API →
Azure Kubernetes ServiceEnd of Life (EOL) Dates & Support Status
Active
Cloud & PlatformsLatest Version: 1.36Latest Release: N/A
Azure Kubernetes Service (AKS) is a managed Kubernetes service on Microsoft Azure.
Support summary
Azure Kubernetes Service 1.34 reaches EOL in 64 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Nov 30, 2026
Azure Kubernetes Service 1.34 · 64 days left
Supported cycles
3
0 lts
Versions
16
Latest Version
1.36
Active Support
3
EOL
13
Lifecycle Timeline
Aug 16, 2023As of Sep 27, 2026
1.36Active · Jun 30, 2027
1.35Active · Mar 31, 2027
1.34Active · Nov 30, 2026
1.33EOL · Jul 31, 2026
1.32EOL · Mar 31, 2026
1.31EOL · Nov 1, 2025
1.30EOL · Aug 22, 2025
1.29EOL · Mar 31, 2025
1.28EOL · Jan 31, 2025
1.27EOL · Jul 31, 2024
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 1.36 | Jun 30, 2026 | Maintained | Jun 30, 2027 | 1.36 | No | Active |
| 1.35 | Mar 5, 2026 | Maintained | Mar 31, 2027 | 1.35 | No | Active |
| 1.34 | Jan 4, 2026 | Maintained | Nov 30, 2026 | 1.34 | No | Active |
| 1.33 | Jun 17, 2025 | Ended | Jul 31, 2026 | 1.33 | No | EOL |
| 1.32 | Apr 6, 2025 | Ended | Mar 31, 2026 | 1.32 | No | EOL |
| 1.31 | Oct 25, 2024 | Ended | Nov 1, 2025 | 1.31 | No | EOL |
| 1.30 | Aug 5, 2024 | Ended | Aug 22, 2025 | 1.30 | No | EOL |
| 1.29 | Mar 18, 2024 | Ended | Mar 31, 2025 | 1.29 | No | EOL |
| 1.28 | Nov 7, 2023 | Ended | Jan 31, 2025 | 1.28 | No | EOL |
| 1.27 | Aug 16, 2023 | Ended | Jul 31, 2024 | 1.27 | No | EOL |
| 1.26 | Apr 18, 2023 | Ended | Apr 11, 2024 | 1.26 | No | EOL |
| 1.25 | Dec 14, 2022 | Ended | Jan 14, 2024 | 1.25 | No | EOL |
| 1.24 | Aug 17, 2022 | Ended | Jul 31, 2023 | 1.24 | No | EOL |
| 1.23 | Apr 26, 2022 | Ended | Apr 2, 2023 | 1.23 | No | EOL |
| 1.22 | Jan 10, 2022 | Ended | Dec 4, 2022 | 1.22 | No | EOL |
| 1.21 | Aug 18, 2021 | Ended | Jul 31, 2022 | 1.21 | No | EOL |
Data sources
Embed this badge
Show Azure Kubernetes Service's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/azure-kubernetes-service/)HTML
<a href="https://eol.wiki/azure-kubernetes-service/"><img src="https://eol.wiki/badge/azure-kubernetes-service.svg" alt="Azure Kubernetes Service end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Azure Kubernetes Service have reached end of life?
The following Azure Kubernetes Service versions have reached end of life and no longer receive security updates: 1.33, 1.32, 1.31, 1.30, 1.29, 1.28, 1.27, 1.26 (and 5 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Azure Kubernetes Service 1.33?
Azure Kubernetes Service 1.33 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Azure Kubernetes Service?
The latest version of Azure Kubernetes Service is 1.36, released in the 1.36 release cycle.
How many versions of Azure Kubernetes Service are currently supported?
Azure Kubernetes Service currently has 3 actively supported version(s): 1.36, 1.35, 1.34.
When does Azure Kubernetes Service 1.36 reach end of life?
Azure Kubernetes Service 1.36 is scheduled to reach end of life on Jun 30, 2027.
What should I do when Azure Kubernetes Service reaches end of life?
When a Azure Kubernetes Service version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.