Skip to content
CI/CD

Argo CD Releases

Track every Argo CD release, from latest stable to end-of-life. Version timelines, EOL dates, security patches, and upgrade guidance for GitOps teams.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Embed Badges

Add live Argo CD status badges to your README, docs, or dashboard.

Health Status

Overall support health

Argo CD Health Status
![Argo CD Health Status](https://img.releaserun.com/badge/health/argo-cd.svg)

EOL Countdown

Next end-of-life date

Argo CD EOL Countdown
![Argo CD EOL Countdown](https://img.releaserun.com/badge/eol/argo-cd.svg)

Latest Version

Current stable release

Argo CD Latest Version
![Argo CD Latest Version](https://img.releaserun.com/badge/v/argo-cd.svg)

CVE Status

Known vulnerabilities

Argo CD CVE Status
![Argo CD CVE Status](https://img.releaserun.com/badge/cve/argo-cd.svg)

Frequently Asked Questions

Common questions about Argo CD releases and lifecycle.

How long are Argo CD versions supported?
Argo CD typically supports the latest three minor releases with security and bug fixes. Older versions are considered end-of-life and do not receive patches.
How often does Argo CD release new versions?
Minor releases ship roughly every 3-4 months. Patch releases with security and bug fixes ship as needed, usually every 2-4 weeks.
What is Argo CD used for?
Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. It syncs your desired application state from Git to your cluster and keeps them in sync automatically.
Should I use Argo CD or Flux CD?
Both are CNCF projects for GitOps on Kubernetes. Argo CD has a built-in UI and application-centric model. Flux takes a more controller-based, infrastructure-as-code approach. Choose based on whether you prefer a UI-driven or Git-driven workflow.

Related Tools