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.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.2 | May 16, 2019 | Nov 13, 2019 | 2461 days past EOL | EOL |
| 1.1 | 1.1.2 | Jul 22, 2019 | Jan 18, 2020 | 2395 days past EOL | EOL |
| 1.2 | 1.2.5 | Sep 4, 2019 | Jan 18, 2020 | 2395 days past EOL | EOL |
| 1.3 | 1.3.6 | Nov 12, 2019 | Jun 17, 2020 | 2244 days past EOL | EOL |
| 1.4 | 1.4.3 | Jan 17, 2020 | Aug 26, 2020 | 2174 days past EOL | EOL |
| 1.5 | 1.5.8 | Apr 2, 2020 | Dec 10, 2020 | 2068 days past EOL | EOL |
| 1.6 | 1.6.2 | Jun 16, 2020 | Dec 15, 2021 | 1698 days past EOL | EOL |
| 1.7 | 1.7.14 | Aug 25, 2020 | Aug 20, 2021 | 1815 days past EOL | EOL |
| 1.8 | 1.8.7 | Dec 9, 2020 | Dec 15, 2021 | 1698 days past EOL | EOL |
| 2.0 | 2.0.5 | Apr 7, 2021 | Mar 6, 2022 | 1617 days past EOL | EOL |
| 2.1 | 2.1.16 | Aug 20, 2021 | Jun 11, 2022 | 1520 days past EOL | EOL |
| 2.2 | 2.2.16 | Dec 14, 2021 | Oct 26, 2022 | 1383 days past EOL | EOL |
| 2.3 | 2.3.17 | Mar 6, 2022 | Feb 7, 2023 | 1279 days past EOL | EOL |
| 2.4 | 2.4.28 | Jun 10, 2022 | May 2, 2023 | 1195 days past EOL | EOL |
| 2.5 | 2.5.22 | Oct 25, 2022 | Aug 7, 2023 | 1098 days past EOL | EOL |
| 2.6 | 2.6.15 | Feb 6, 2023 | Nov 5, 2023 | 1008 days past EOL | EOL |
| 2.7 | 2.7.18 | May 1, 2023 | Feb 5, 2024 | 916 days past EOL | EOL |
| 2.8 | 2.8.21 | Aug 7, 2023 | May 7, 2024 | 824 days past EOL | EOL |
| 2.9 | 2.9.22 | Nov 5, 2023 | Aug 5, 2024 | 734 days past EOL | EOL |
| 2.10 | 2.10.20 | Feb 5, 2024 | Nov 4, 2024 | 643 days past EOL | EOL |
| 2.11 | 2.11.14 | May 7, 2024 | Feb 3, 2025 | 552 days past EOL | EOL |
| 2.12 | 2.12.13 | Aug 5, 2024 | May 6, 2025 | 460 days past EOL | EOL |
| 2.13 | 2.13.9 | Nov 4, 2024 | Aug 13, 2025 | 361 days past EOL | EOL |
| 2.14 | 2.14.21 | Feb 3, 2025 | Nov 4, 2025 | 278 days past EOL | EOL |
| 3.0 | 3.0.23 | May 6, 2025 | Feb 2, 2026 | 188 days past EOL | EOL |
| 3.1 | 3.1.16 | Aug 13, 2025 | May 5, 2026 | 96 days past EOL | EOL |
| 3.2 | 3.2.12 | Nov 4, 2025 | Aug 4, 2026 | 5 days past EOL | EOL |
| 3.3 | 3.3.13 | Feb 2, 2026 | TBD | Supported | Active |
| 3.4 | 3.4.6 | May 5, 2026 | TBD | Supported | Active |
| 3.5 | 3.5.0 | Aug 4, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/argo-cd)
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.
Your options when Argo CD reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
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.
Argo CD has 27 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Argo CD exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.