Complete end-of-life dates, support windows, and security status for all Kubernetes versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.16 | 1.16.15 | Sep 18, 2019 | Aug 4, 2020 | 2104 days past EOL | EOL |
| 1.17 | 1.17.17 | Dec 7, 2019 | Dec 25, 2020 | 1961 days past EOL | EOL |
| 1.18 | 1.18.20 | Mar 25, 2020 | Jun 18, 2021 | 1786 days past EOL | EOL |
| 1.19 | 1.19.16 | Aug 26, 2020 | Oct 28, 2021 | 1654 days past EOL | EOL |
| 1.20 | 1.20.15 | Dec 8, 2020 | Feb 28, 2022 | 1531 days past EOL | EOL |
| 1.21 | 1.21.14 | Apr 8, 2021 | Jun 28, 2022 | 1411 days past EOL | EOL |
| 1.22 | 1.22.17 | Aug 4, 2021 | Oct 28, 2022 | 1289 days past EOL | EOL |
| 1.23 | 1.23.17 | Dec 7, 2021 | Feb 28, 2023 | 1166 days past EOL | EOL |
| 1.24 | 1.24.17 | May 3, 2022 | Jul 28, 2023 | 1016 days past EOL | EOL |
| 1.25 | 1.25.16 | Aug 23, 2022 | Oct 27, 2023 | 925 days past EOL | EOL |
| 1.26 | 1.26.15 | Dec 8, 2022 | Feb 28, 2024 | 801 days past EOL | EOL |
| 1.27 | 1.27.16 | Apr 11, 2023 | Jun 28, 2024 | 680 days past EOL | EOL |
| 1.28 | 1.28.15 | Aug 15, 2023 | Oct 28, 2024 | 558 days past EOL | EOL |
| 1.29 | 1.29.15 | Dec 13, 2023 | Feb 28, 2025 | 435 days past EOL | EOL |
| 1.30 | 1.30.14 | Apr 17, 2024 | Jun 28, 2025 | 315 days past EOL | EOL |
| 1.31 | 1.31.14 | Aug 13, 2024 | Oct 28, 2025 | 193 days past EOL | EOL |
| 1.32 | 1.32.13 | Dec 11, 2024 | Feb 28, 2026 | 70 days past EOL | EOL |
| 1.33 | 1.33.11 | Apr 23, 2025 | Jun 28, 2026 | 50 days remaining | Warning |
| 1.34 | 1.34.7 | Aug 27, 2025 | Oct 27, 2026 | 171 days remaining | Warning |
| 1.35 | 1.35.4 | Dec 17, 2025 | Feb 28, 2027 | 295 days remaining | Active |
When a Kubernetes 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 Kubernetes 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 →