Complete end-of-life dates, support windows, and security status for all Karpenter versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.8 | Aug 14, 2024 | Jan 28, 2025 | 466 days past EOL | EOL |
| 1.1 | 1.1.4 | Nov 30, 2024 | Mar 4, 2025 | 431 days past EOL | EOL |
| 1.2 | 1.2.4 | Jan 28, 2025 | Apr 16, 2025 | 388 days past EOL | EOL |
| 1.3 | 1.3.4 | Mar 4, 2025 | May 24, 2025 | 350 days past EOL | EOL |
| 1.4 | 1.4.1 | Apr 16, 2025 | Jul 14, 2025 | 299 days past EOL | EOL |
| 1.5 | 1.5.4 | May 24, 2025 | Sep 16, 2025 | 235 days past EOL | EOL |
| 1.6 | 1.6.3 | Jul 14, 2025 | Oct 8, 2025 | 213 days past EOL | EOL |
| 1.7 | 1.7.1 | Sep 16, 2025 | Feb 6, 2026 | 92 days past EOL | EOL |
| 1.8 | 1.8.2 | Oct 8, 2025 | Jan 15, 2026 | 114 days past EOL | EOL |
| 1.9 | 1.9.0 | Feb 6, 2026 | Mar 20, 2026 | 50 days past EOL | EOL |
| 1.10 | 1.10.0 | Mar 20, 2026 | Apr 6, 2026 | 33 days past EOL | EOL |
| 1.11 | 1.11.1 | Apr 6, 2026 | Already EOL | Supported | Active |
When a Karpenter 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 Karpenter 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 →