Kubernetes 1.28 · Version Status
Kubernetes 1.28 End of Life Date
Kubernetes 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.
⚠
Kubernetes 1.28 is past end of life. This version no longer receives security patches. 690 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 22, 2024
690 days past EOL
Latest Release
1.28.15
Standard release
Release Date
Aug 15, 2023
Kubernetes 1.28 series
Lifecycle detail
Kubernetes 1.28 was released on August 15, 2023 and support ended on October 22, 2024 — a supported lifespan of 1 year and 2 months, in line with the 1 year and 3 months median for Kubernetes releases. The last patch it will ever receive is 1.28.15, published October 22, 2024 — on the day support ended. It has been without security patches for 1 year and 11 months. 6 newer Kubernetes releases have shipped since.
Attack Surface
30/30 Critical 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 Kubernetes 1.28 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.16 |
1.16.15 |
Sep 2, 2020 |
EOL |
| 1.17 |
1.17.17 |
Jan 13, 2021 |
EOL |
| 1.18 |
1.18.20 |
Jun 18, 2021 |
EOL |
| 1.19 |
1.19.16 |
Oct 28, 2021 |
EOL |
| 1.20 |
1.20.15 |
Feb 28, 2022 |
EOL |
| 1.21 |
1.21.14 |
Jun 28, 2022 |
EOL |
| 1.22 |
1.22.17 |
Dec 8, 2022 |
EOL |
| 1.23 |
1.23.17 |
Feb 28, 2023 |
EOL |
What does Kubernetes 1.28 end of life mean?
When Kubernetes 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 Kubernetes 1.28 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Kubernetes 1.37 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Kubernetes 1.28 reach end of life?
Kubernetes 1.28 reached end of life on October 22, 2024. This version is no longer receiving security patches.
Is Kubernetes 1.28 still supported?
No. Kubernetes 1.28 reached end of life on October 22, 2024 and is no longer receiving security patches.
What should I upgrade to from Kubernetes 1.28?
The recommended upgrade from Kubernetes 1.28 is
Kubernetes 1.37 — the latest actively supported version. Check the
Kubernetes full timeline for all supported versions.
What are the security risks of running Kubernetes 1.28 past EOL?
When Kubernetes 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 Kubernetes should migrate immediately or implement compensating controls.
Does Kubernetes track end-of-life by point release (e.g. Kubernetes 1.37.1, Kubernetes 1.37.2)?
No — Kubernetes end-of-life dates apply to the entire 1.37.x release series, not individual point releases. A point release like Kubernetes 1.37.1 or Kubernetes 1.37.2 shares the same EOL date as Kubernetes 1.37. Security patches stop for the entire 1.37.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.