Azure Kubernetes Service 1.35 · Version Status
Azure Kubernetes Service 1.35 End of Life Date
Azure Kubernetes Service 1.35 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Azure Kubernetes Service 1.35 is actively supported. EOL date: March 31, 2027.
📅 Get reminded before Azure Kubernetes Service 1.35 reaches EOL on March 31, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Mar 31, 2027
202 days remaining
Latest Release
—
Standard release
Release Date
Mar 5, 2026
Azure Kubernetes Service 1.35 series
Extended Support
Mar 31, 2028
AKS Long Term Support · paid
Lifecycle detail
Azure Kubernetes Service 1.35 was released on March 5, 2026 and support is scheduled to end on March 31, 2027 — a planned supported lifespan of 1 year and 1 month, in line with the 1 year median for Azure Kubernetes Service releases.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Azure Kubernetes Service Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.21 |
— |
Jul 31, 2022 |
EOL |
| 1.22 |
— |
Dec 4, 2022 |
EOL |
| 1.23 |
— |
Apr 2, 2023 |
EOL |
| 1.24 |
— |
Jul 31, 2023 |
EOL |
| 1.25 |
— |
Jan 14, 2024 |
EOL |
| 1.26 |
— |
Apr 11, 2024 |
EOL |
| 1.27 |
— |
Jul 31, 2024 |
EOL |
| 1.28 |
— |
Jan 31, 2025 |
EOL |
What does Azure Kubernetes Service 1.35 end of life mean?
When Azure Kubernetes Service 1.35 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Azure Kubernetes Service 1.35 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Azure Kubernetes Service 1.36 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Azure Kubernetes Service 1.35 reach end of life?
Azure Kubernetes Service 1.35 reached end of life on March 31, 2027. That is 202 days remaining.
Is Azure Kubernetes Service 1.35 still supported?
Yes, Azure Kubernetes Service 1.35 is currently supported. The EOL date is March 31, 2027.
What should I upgrade to from Azure Kubernetes Service 1.35?
The recommended upgrade from Azure Kubernetes Service 1.35 is
Azure Kubernetes Service 1.36 — the latest actively supported version. Check the
Azure Kubernetes Service full timeline for all supported versions.
What are the security risks of running Azure Kubernetes Service 1.35 past EOL?
When Azure Kubernetes Service 1.35 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Azure Kubernetes Service should migrate immediately or implement compensating controls.