GitOps

Argo CD Releases

Track Argo CD releases, Kubernetes version compatibility, feature evolution, and upgrade guidance. GitOps workflow changes, ApplicationSet improvements, and Flux CD comparison.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

2.7

2.8

2.9

2.10

2.11

2.12

2.13

2023 2024 2025 2026 2027 2028

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active / LTS

Maintenance

Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

2.8/2.9 2.12+ Medium Difficulty

Est. 1-2 hours per version hop

Breaking Changes

ApplicationSet controller merged into argocd-server (2.11+)
Deprecated sync options removed
RBAC policy syntax changes for ApplicationSets
Notification controller consolidated
Health assessment behavior changes for some resources
Helm value file handling stricter

Migration Notes

Upgrade one minor version at a time. The ApplicationSet controller merge in 2.11 is the biggest change: if you deployed it separately, you need to remove the standalone deployment. RBAC policies for ApplicationSets may need updating. Test in a non-production cluster first.

2.11/2.12 2.13 Low Difficulty

Est. 30-60 minutes

Breaking Changes

Updated default sync retry behavior
New ApplicationSet generator options
Enhanced multi-source Application handling

Migration Notes

Straightforward upgrade. Update Helm chart or kustomize manifests, apply, verify. No architectural changes. Check the changelog for any deprecated features you rely on.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version	EOL Risk	CVE Risk	Ecosystem	Cloud Support	Overall	Recommended Action
Argo CD 2.9 and older	Critical	High	Unsupported	None	Critical	No patches — upgrade through each minor version
Argo CD 2.10	Critical	Medium	Unsupported	Degrading	Critical	Past EOL — upgrade to 2.12+
Argo CD 2.11	High	Low	Maintenance	Full	Medium	Security-only — plan upgrade
Argo CD 2.12	Low	Low	Active	Full	Low	Current supported — recommended
Argo CD 2.13	None	Low	Active	Full	Low	Latest — recommended for new installs

Argo CD supports the latest 3 minor versions. Older versions receive no patches. Assessed March 2026.

Argo CD Version Feature Comparison

Side-by-side feature differences across major versions.

Feature	2.8	2.9	2.10	2.11	2.12
ApplicationSet controller	Separate	Separate	Separate	Merged	Merged
Multi-source Applications	Beta	Beta	Stable	Stable	Enhanced
Server-side diff	No	Beta	Stable	Stable	Stable
Notifications controller	Separate	Separate	Merged	Merged	Merged
Web terminal	Stable	Stable	Stable	Stable	Enhanced
RBAC for ApplicationSets	Basic	Basic	Improved	Enhanced	Enhanced
Helm OCI registry support	Stable	Stable	Stable	Enhanced	Enhanced
K8s version support	1.25-1.28	1.26-1.29	1.27-1.30	1.27-1.31	1.28-1.31
Progressive syncs	No	No	Beta	Stable	Enhanced

Embed Badges

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

Health Status

Overall support health

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

EOL Countdown

Next end-of-life date

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

Latest Version

Current stable release

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

CVE Status

Known vulnerabilities

![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 does Argo CD versioning and support work?

Argo CD maintains the latest 3 minor versions with bug fixes and security patches. Each minor release is supported for approximately 6 months. When a new minor releases, the oldest of the 3 drops to EOL. Patch releases come out as needed. The project follows a roughly quarterly release cadence for minor versions.

Which Kubernetes versions does Argo CD support?

Each Argo CD minor version is tested against specific Kubernetes versions. Generally, Argo CD supports the last 3-4 Kubernetes minor versions. Argo CD 2.12+ supports K8s 1.27-1.31. Running Argo CD on an unsupported K8s version may work but is not guaranteed. Check the compatibility matrix in the docs for your specific version.

What is the difference between Argo CD and Flux CD?

Both are CNCF GitOps tools. Argo CD provides a rich web UI, RBAC, SSO integration, and multi-cluster management out of the box. Flux is more lightweight and Kubernetes-native (CRDs for everything, no web UI by default). Argo CD is better for teams that want a visual dashboard. Flux is better for teams that prefer pure CLI/GitOps and want tighter K8s integration. Both are production-grade.

What are ApplicationSets?

ApplicationSets automate the creation of Argo CD Applications from templates. Instead of manually creating 50 Applications for 50 microservices, you define one ApplicationSet with a generator (Git directory, cluster list, matrix, etc.) that produces Applications dynamically. They are essential for managing multi-cluster and multi-tenant deployments at scale.

How do I upgrade Argo CD safely?

Upgrade one minor version at a time. Read the upgrade notes for each version. Back up your Argo CD configuration (argocd-cm, argocd-rbac-cm ConfigMaps and the argocd-secret). Apply the new manifests or update the Helm chart. Argo CD supports zero-downtime upgrades with multiple replicas. After upgrading, verify the /healthz endpoint and check that all Applications still sync.

Can Argo CD manage itself (self-manage)?

Yes, and this is a recommended pattern. Argo CD can manage its own deployment via an Application that points to its Helm chart or manifests. This means Argo CD upgrades are just Git commits. Use the "app of apps" pattern: one root Application that manages Argo CD plus all other Applications. Be careful with breaking changes that could lock you out.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.