Complete end-of-life dates, support windows, and security status for all Google Kubernetes Engine versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.17 | 1.17.17-gke.9100 | Mar 29, 2021 | Nov 1, 2021 | 1650 days past EOL | EOL |
| 1.18 | 1.18.20-gke.6000 | Mar 29, 2021 | Mar 1, 2022 | 1530 days past EOL | EOL |
| 1.19 | 1.19.16-gke.15700 | Apr 14, 2021 | Jun 1, 2022 | 1438 days past EOL | EOL |
| 1.20 | 1.20.15-gke.13700 | Jun 9, 2021 | Aug 1, 2022 | 1377 days past EOL | EOL |
| 1.21 | 1.21.14-gke.18800 | Oct 1, 2021 | Jan 31, 2023 | 1194 days past EOL | EOL |
| 1.22 | 1.22.17-gke.14100 | Mar 7, 2022 | Apr 30, 2023 | 1105 days past EOL | EOL |
| 1.23 | 1.23.17-gke.10700 | May 3, 2022 | Jul 31, 2023 | 1013 days past EOL | EOL |
| 1.24 | 1.24.17-gke.2472000 | Jun 23, 2022 | Oct 31, 2023 | 921 days past EOL | EOL |
| 1.25 | 1.25.16-gke.1759000 | Dec 14, 2022 | Mar 30, 2024 | 770 days past EOL | EOL |
| 1.26 | 1.26.15-gke.1469001 | Mar 31, 2023 | Jun 30, 2024 | 678 days past EOL | EOL |
| 1.27 | 1.27.16-gke.2894000 | Jun 15, 2023 | Oct 1, 2024 | 585 days past EOL | EOL |
| 1.28 | 1.28.15-gke.3290000 | Dec 4, 2023 | Feb 4, 2025 | 459 days past EOL | EOL |
| 1.29 | 1.29.15-gke.2725000 | Jan 26, 2024 | Apr 12, 2025 | 392 days past EOL | EOL |
| 1.30 | 1.30.14-gke.2441000 | Jul 31, 2024 | Sep 30, 2025 | 221 days past EOL | EOL |
| 1.31 | 1.31.14-gke.1850000 | Oct 25, 2024 | Jan 16, 2026 | 113 days past EOL | EOL |
| 1.32 | 1.32.13-gke.1449000 | Feb 11, 2025 | Apr 11, 2026 | 28 days past EOL | EOL |
| 1.33 | 1.33.11-gke.1137000 | Jun 3, 2025 | Aug 3, 2026 | 86 days remaining | Warning |
| 1.34 | 1.34.7-gke.1321000 | Sep 30, 2025 | Oct 1, 2026 | 145 days remaining | Warning |
| 1.35 | 1.35.3-gke.1993000 | Feb 11, 2026 | Apr 11, 2027 | 337 days remaining | Active |
When a Google Kubernetes Engine 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 Google Kubernetes Engine 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 →