Azure Kubernetes Service 1.28 · Version Status
Azure Kubernetes Service 1.28 End of Life Date
Azure Kubernetes Service 1.28 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.28 is past end of life. This version no longer receives security patches. 587 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 31, 2025
587 days past EOL
Latest Release
—
Standard release
Release Date
Nov 7, 2023
Azure Kubernetes Service 1.28 series
Extended Support
Feb 28, 2026
AKS Long Term Support · paid · ended
Lifecycle detail
Azure Kubernetes Service 1.28 was released on November 7, 2023 and support ended on January 31, 2025 — a supported lifespan of 1 year and 3 months, longer than the 1 year median for Azure Kubernetes Service releases. It has been without security patches for 1 year and 7 months. 5 newer Azure Kubernetes Service releases have shipped since.
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 →
Extended Support
Extended Azure Kubernetes Service 1.28 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
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.28 end of life mean?
When Azure Kubernetes Service 1.28 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.28 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.28 reach end of life?
Azure Kubernetes Service 1.28 reached end of life on January 31, 2025. This version is no longer receiving security patches.
Is Azure Kubernetes Service 1.28 still supported?
No. Azure Kubernetes Service 1.28 reached end of life on January 31, 2025 and is no longer receiving security patches.
What should I upgrade to from Azure Kubernetes Service 1.28?
The recommended upgrade from Azure Kubernetes Service 1.28 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.28 past EOL?
When Azure Kubernetes Service 1.28 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.