Argo CD End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Argo CD 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.2 | May 16, 2019 | Nov 13, 2019 | 2414 days past EOL | EOL |
| 1.1 | 1.1.2 | Jul 22, 2019 | Jan 18, 2020 | 2348 days past EOL | EOL |
| 1.2 | 1.2.5 | Sep 4, 2019 | Jan 18, 2020 | 2348 days past EOL | EOL |
| 1.3 | 1.3.6 | Nov 12, 2019 | Jun 17, 2020 | 2197 days past EOL | EOL |
| 1.4 | 1.4.3 | Jan 17, 2020 | Aug 26, 2020 | 2127 days past EOL | EOL |
| 1.5 | 1.5.8 | Apr 2, 2020 | Dec 10, 2020 | 2021 days past EOL | EOL |
| 1.6 | 1.6.2 | Jun 16, 2020 | Dec 15, 2021 | 1651 days past EOL | EOL |
| 1.7 | 1.7.14 | Aug 25, 2020 | Aug 20, 2021 | 1768 days past EOL | EOL |
| 1.8 | 1.8.7 | Dec 9, 2020 | Dec 15, 2021 | 1651 days past EOL | EOL |
| 2.0 | 2.0.5 | Apr 7, 2021 | Mar 6, 2022 | 1570 days past EOL | EOL |
| 2.1 | 2.1.16 | Aug 20, 2021 | Jun 11, 2022 | 1473 days past EOL | EOL |
| 2.2 | 2.2.16 | Dec 14, 2021 | Oct 26, 2022 | 1336 days past EOL | EOL |
| 2.3 | 2.3.17 | Mar 6, 2022 | Feb 7, 2023 | 1232 days past EOL | EOL |
| 2.4 | 2.4.28 | Jun 10, 2022 | May 2, 2023 | 1148 days past EOL | EOL |
| 2.5 | 2.5.22 | Oct 25, 2022 | Aug 7, 2023 | 1051 days past EOL | EOL |
| 2.6 | 2.6.15 | Feb 6, 2023 | Nov 5, 2023 | 961 days past EOL | EOL |
| 2.7 | 2.7.18 | May 1, 2023 | Feb 5, 2024 | 869 days past EOL | EOL |
| 2.8 | 2.8.21 | Aug 7, 2023 | May 7, 2024 | 777 days past EOL | EOL |
| 2.9 | 2.9.22 | Nov 5, 2023 | Aug 5, 2024 | 687 days past EOL | EOL |
| 2.10 | 2.10.20 | Feb 5, 2024 | Nov 4, 2024 | 596 days past EOL | EOL |
| 2.11 | 2.11.14 | May 7, 2024 | Feb 3, 2025 | 505 days past EOL | EOL |
| 2.12 | 2.12.13 | Aug 5, 2024 | May 6, 2025 | 413 days past EOL | EOL |
| 2.13 | 2.13.9 | Nov 4, 2024 | Aug 13, 2025 | 314 days past EOL | EOL |
| 2.14 | 2.14.21 | Feb 3, 2025 | Nov 4, 2025 | 231 days past EOL | EOL |
| 3.0 | 3.0.23 | May 6, 2025 | Feb 2, 2026 | 141 days past EOL | EOL |
| 3.1 | 3.1.16 | Aug 13, 2025 | May 5, 2026 | 49 days past EOL | EOL |
| 3.2 | 3.2.12 | Nov 4, 2025 | TBD | Supported | Active |
| 3.3 | 3.3.12 | Feb 2, 2026 | TBD | Supported | Active |
| 3.4 | 3.4.4 | May 5, 2026 | TBD | Supported | Active |
What does Argo CD end of life mean for your organization?
When a version of Argo CD 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 Argo CD 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Argo CD versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →