EOL.WikiEOL.Wiki
← ← Back to all products

Argo CDEnd of Life (EOL) Dates & Support Status

Active
DevOps & CI/CDLatest Version: 3.5.3Latest Release: Sep 14, 2026

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes applications.

Support summary

Argo CD currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

3

0 lts

Versions

30

Latest Version

3.5.3

Active Support

3

EOL

27

Lifecycle Timeline

May 7, 2024As of Sep 27, 2026
3.5Active · Date not announced
3.4Active · Date not announced
3.3Active · Date not announced
3.2EOL · Aug 4, 2026
3.1EOL · May 5, 2026
3.0EOL · Feb 2, 2026
2.14EOL · Nov 4, 2025
2.13EOL · Aug 13, 2025
2.12EOL · May 6, 2025
2.11EOL · Feb 3, 2025
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.5Aug 4, 2026MaintainedDate not announced3.5.3No
Active
3.4May 5, 2026MaintainedDate not announced3.4.9No
Active
3.3Feb 2, 2026MaintainedDate not announced3.3.14No
Active
3.2Nov 4, 2025EndedAug 4, 20263.2.12No
EOL
3.1Aug 13, 2025EndedMay 5, 20263.1.16No
EOL
3.0May 6, 2025EndedFeb 2, 20263.0.23No
EOL
2.14Feb 3, 2025EndedNov 4, 20252.14.21No
EOL
2.13Nov 4, 2024EndedAug 13, 20252.13.9No
EOL
2.12Aug 5, 2024EndedMay 6, 20252.12.13No
EOL
2.11May 7, 2024EndedFeb 3, 20252.11.14No
EOL
2.10Feb 5, 2024EndedNov 4, 20242.10.20No
EOL
2.9Nov 5, 2023EndedAug 5, 20242.9.22No
EOL
2.8Aug 7, 2023EndedMay 7, 20242.8.21No
EOL
2.7May 1, 2023EndedFeb 5, 20242.7.18No
EOL
2.6Feb 6, 2023EndedNov 5, 20232.6.15No
EOL
2.5Oct 25, 2022EndedAug 7, 20232.5.22No
EOL
2.4Jun 10, 2022EndedMay 2, 20232.4.28No
EOL
2.3Mar 6, 2022EndedFeb 7, 20232.3.17No
EOL
2.2Dec 14, 2021EndedOct 26, 20222.2.16No
EOL
2.1Aug 20, 2021EndedJun 11, 20222.1.16No
EOL
2.0Apr 7, 2021EndedMar 6, 20222.0.5No
EOL
1.8Dec 9, 2020EndedDec 15, 20211.8.7No
EOL
1.7Aug 25, 2020EndedAug 20, 20211.7.14No
EOL
1.6Jun 16, 2020EndedDec 15, 20211.6.2No
EOL
1.5Apr 2, 2020EndedDec 10, 20201.5.8No
EOL
1.4Jan 17, 2020EndedAug 26, 20201.4.3No
EOL
1.3Nov 12, 2019EndedJun 17, 20201.3.6No
EOL
1.2Sep 4, 2019EndedJan 18, 20201.2.5No
EOL
1.1Jul 22, 2019EndedJan 18, 20201.1.2No
EOL
1.0May 16, 2019EndedNov 13, 20191.0.2No
EOL

Data sources

Embed this badge

Argo CD end-of-life support status badge

Show Argo CD's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Argo CD end-of-life status](https://eol.wiki/badge/argo-cd.svg)](https://eol.wiki/argo-cd/)

HTML

<a href="https://eol.wiki/argo-cd/"><img src="https://eol.wiki/badge/argo-cd.svg" alt="Argo CD end-of-life status" height="20"></a>
All badges & lifecycle API →

Frequently Asked Questions

Which versions of Argo CD have reached end of life?
The following Argo CD versions have reached end of life and no longer receive security updates: 3.2, 3.1, 3.0, 2.14, 2.13, 2.12, 2.11, 2.10 (and 19 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Argo CD 3.2?
Argo CD 3.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Argo CD?
The latest version of Argo CD is 3.5.3, released in the 3.5 release cycle.
How many versions of Argo CD are currently supported?
Argo CD currently has 3 actively supported version(s): 3.5, 3.4, 3.3.
When does Argo CD 3.5 reach end of life?
Argo CD 3.5 does not have a specific end-of-life date announced yet.
What should I do when Argo CD reaches end of life?
When a Argo CD version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.