Complete end-of-life dates, support windows, and security status for all Azure Kubernetes Service versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.21 | — | Aug 18, 2021 | Jul 31, 2022 | 1378 days past EOL | EOL |
| 1.22 | — | Jan 10, 2022 | Dec 4, 2022 | 1252 days past EOL | EOL |
| 1.23 | — | Apr 26, 2022 | Apr 2, 2023 | 1133 days past EOL | EOL |
| 1.24 | — | Aug 17, 2022 | Jul 31, 2023 | 1013 days past EOL | EOL |
| 1.25 | — | Dec 14, 2022 | Jan 14, 2024 | 846 days past EOL | EOL |
| 1.26 | — | Apr 18, 2023 | Apr 11, 2024 | 758 days past EOL | EOL |
| 1.27 | — | Aug 16, 2023 | Jul 31, 2024 | 647 days past EOL | EOL |
| 1.28 | — | Nov 7, 2023 | Jan 31, 2025 | 463 days past EOL | EOL |
| 1.29 | — | Mar 18, 2024 | Mar 31, 2025 | 404 days past EOL | EOL |
| 1.30 | — | Aug 5, 2024 | Aug 22, 2025 | 260 days past EOL | EOL |
| 1.31 | — | Oct 25, 2024 | Nov 1, 2025 | 189 days past EOL | EOL |
| 1.32 | — | Apr 6, 2025 | Mar 31, 2026 | 39 days past EOL | EOL |
| 1.33 | — | Jun 17, 2025 | Jun 30, 2026 | 52 days remaining | Warning |
| 1.34 | — | Jan 4, 2026 | Nov 30, 2026 | 205 days remaining | Active |
| 1.35 | — | Mar 5, 2026 | Mar 31, 2027 | 326 days remaining | Active |
When a Azure Kubernetes Service version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Azure Kubernetes Service should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →