Question 1

What happens when Argo Cd reaches end of life?

Accepted Answer

When Argo Cd reaches end of life, it stops receiving security patches, bug fixes, and new features. Currently, 26 Argo Cd versions are already EOL. The latest supported version is Argo Cd 3.4. Running an EOL version exposes your systems to unpatched security vulnerabilities with no official fix available.

Question 2

Is Argo Cd 3.4 still supported?

Accepted Answer

Yes. Argo Cd 3.4 is actively supported. It receives security patches and bug fixes. Check the version table above for the full list of supported Argo Cd releases and their exact end-of-life dates.

Question 3

Is it safe to use Argo Cd after end of life?

Accepted Answer

No. Running Argo Cd after EOL is not safe for production systems. Once a version reaches end of life, newly discovered CVEs are published publicly but never patched — leaving your systems permanently exposed. The only safe path is upgrading to an actively supported Argo Cd release.

Question 4

How to upgrade from Argo Cd 3.1 to Argo Cd 3.x?

Accepted Answer

To upgrade Argo Cd from 3.1 to 3.4: (1) review the official migration guide for breaking changes, (2) test your application against the new version in a staging environment, (3) update dependencies that have version constraints, (4) run your full test suite, (5) deploy with a rollback plan. The earlier you start, the more time you have to resolve compatibility issues before EOL.

Question 5

When is the next Argo Cd LTS version?

Accepted Answer

Not all Argo Cd releases have a designated LTS status. Check the version table above — LTS releases are marked with an "LTS" badge. Refer to the official Argo Cd release policy for information on upcoming long-term support versions.

Question 6

How long does Argo Cd support each version?

Accepted Answer

On average, Argo Cd supports each release for approximately 9 months (~0.8 years).  The exact EOL date for each version is listed in the table above.

Version	Released	Active support	EOL date	Until EOL	Latest	CVEs	Status
3.4	May 5, 2026	—	No	—	3.4.3	—	Active
3.3	Feb 2, 2026	—	No	—	3.3.11	—	Active
3.2	Nov 4, 2025	—	No	—	3.2.12	—	Active
3.1	Aug 13, 2025	—	May 5, 2026	35d ago	3.1.16	—	EOL
3.0	May 6, 2025	—	Feb 2, 2026	127d ago	3.0.23	—	EOL
2.14	Feb 3, 2025	—	Nov 4, 2025	217d ago	2.14.21	—	EOL
2.13	Nov 4, 2024	—	Aug 13, 2025	300d ago	2.13.9	—	EOL
2.12	Aug 5, 2024	—	May 6, 2025	399d ago	2.12.13	—	EOL
2.11	May 7, 2024	—	Feb 3, 2025	491d ago	2.11.14	—	EOL
2.10	Feb 5, 2024	—	Nov 4, 2024	582d ago	2.10.20	—	EOL
2.9	Nov 5, 2023	—	Aug 5, 2024	673d ago	2.9.22	—	EOL
2.8	Aug 7, 2023	—	May 7, 2024	763d ago	2.8.21	—	EOL
2.7	May 1, 2023	—	Feb 5, 2024	855d ago	2.7.18	—	EOL
2.6	Feb 6, 2023	—	Nov 5, 2023	947d ago	2.6.15	—	EOL
2.5	Oct 25, 2022	—	Aug 7, 2023	1037d ago	2.5.22	—	EOL
2.4	Jun 10, 2022	—	May 2, 2023	1134d ago	2.4.28	—	EOL
2.3	Mar 6, 2022	—	Feb 7, 2023	1218d ago	2.3.17	—	EOL
2.2	Dec 14, 2021	—	Oct 26, 2022	1322d ago	2.2.16	—	EOL
2.1	Aug 20, 2021	—	Jun 11, 2022	1459d ago	2.1.16	—	EOL
2.0	Apr 7, 2021	—	Mar 6, 2022	1556d ago	2.0.5	—	EOL
1.8	Dec 9, 2020	—	Dec 15, 2021	1637d ago	1.8.7	—	EOL
1.7	Aug 25, 2020	—	Aug 20, 2021	1754d ago	1.7.14	—	EOL
1.6	Jun 16, 2020	—	Dec 15, 2021	1637d ago	1.6.2	—	EOL
1.5	Apr 2, 2020	—	Dec 10, 2020	2007d ago	1.5.8	—	EOL
1.4	Jan 17, 2020	—	Aug 26, 2020	2113d ago	1.4.3	—	EOL
1.3	Nov 12, 2019	—	Jun 17, 2020	2183d ago	1.3.6	—	EOL
1.2	Sep 4, 2019	—	Jan 18, 2020	2334d ago	1.2.5	—	EOL
1.1	Jul 22, 2019	—	Jan 18, 2020	2334d ago	1.1.2	—	EOL
1.0	May 16, 2019	—	Nov 13, 2019	2400d ago	1.0.2	—	EOL

Argo Cd End of Life Dates

Related technologies

Same category

Frequently Asked Questions