GitOps with Argo CD: Latest Developments 2025/2026

📷 "container ship leaving bay area" by Derell Licht is licensed under CC BY-ND 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-nd/2.0/.

Anyone managing Kubernetes clusters in production knows the challenge: updates, rollbacks, and environment changes must be reliable, traceable, and repeatable. The GitOps paradigm has established itself as the standard in recent years – and Argo CD as the most widely used tool. A recent CNCF survey shows: Argo CD runs in nearly 60 percent of all Kubernetes clusters and achieves a Net Promoter Score (NPS) of 79 – an exceptionally high value for an open-source infrastructure component.

Argo CD 3.0 and the Current Release Status

In March 2025, the Argo project released the first release candidate of Argo CD 3.0 – the first major version since 2021. The changes primarily target security, better defaults, and the removal of deprecated components. The most important innovations include a fine-grained RBAC model that controls permissions not only at the application level but also at the resource level, as well as improved resource tracking. The handling of secrets – always a sensitive topic in GitOps workflows – was also addressed with clear recommendations and security improvements.

The current stable release is Argo CD v3.4.5 (July 2026), which includes, among other things, a fix for auto-sync issues with simultaneous commits and improvements in Server-Side Apply (SSA). In parallel, the community is working on version 3.5, which is already in the release candidate stage (v3.5.0-rc2).

Those updating from Argo CD 2.x to 3.0 will find a detailed upgrade guide in the official documentation. The migration is classified as low-risk – only a few, clearly documented breaking changes are expected.

CNCF Graduation and Community Growth

The Argo project was elevated to Graduated Status by the CNCF on December 6, 2022 – the highest maturity level. Since then, community growth has been unbroken: the project now counts over 15,400 contributors and 3,300 organizations. The 2025 CNCF End-User Survey confirms that 97 percent of respondents use Argo CD in production, 60 percent of them for more than two years. Platform engineers represent the largest user group at 37 percent – an indication of Argo CD’s strategic role in Internal Developer Platforms (IDPs).

ApplicationSets – Multi-Cluster and Multi-Application at the Push of a Button

A central feature for operation in larger environments are ApplicationSets. They allow the declarative definition of application templates that are automatically extended to multiple clusters or environments via generators (e.g., Cluster Generator, Git Generator, Matrix Generator). The CNCF survey shows: 42 percent of teams manage over 500 applications per Argo CD instance, 25 percent connect more than 20 clusters. ApplicationSets are the key to this scalability.

Argo Rollouts – Progressive Delivery

While Argo CD controls the synchronization between Git and the cluster, Argo Rollouts handles Progressive Delivery – i.e., canary and blue-green deployments with automated analysis. Rollouts replaces the native Kubernetes Deployment with its own CRD, enabling traffic control via Ingress controllers or service meshes, automated metric analysis (Prometheus, Datadog, Webhooks), and manual promote/abort decisions. This feature has proven indispensable, especially in security-critical environments – such as financial service providers or e-commerce.

Config Management Plugins and Extensibility

Not every team uses Helm or Kustomize. Argo CD therefore supports Config Management Plugins (CMPs) as sidecar containers in the repository server. This allows any tools like CUE, YTT, Tanka, or jsonnet to be integrated without modifying the Argo CD core. Since version 2.6, there is a revised CMPv2 interface that ensures a clean separation between plugin logic and Argo CD code.

Security and RBAC

Security was a focus of Argo CD 3.0’s development. The new RBAC model allows fine-grained permissions at the resource level within an application – for example, “may delete pods, but not modify deployments.” Argo CD also relies on signed container images (Cosign) and SLSA Level 3 provenance, making build pipelines fully traceable.

Differentiation from Flux CD

The question “Argo CD or Flux CD?” is frequently discussed in the DevOps environment. While Flux scores points as a lightweight, CLI-driven approach and offers a smaller attack surface due to its decentralized architecture model, Argo CD convinces with its web UI, integrated multi-cluster management, RBAC, and shorter onboarding time. For teams that need centralized visibility across multiple clusters and environments, Argo CD is currently the first choice.

Conclusion

Argo CD has evolved from a CNCF-incubated project to the de facto standard for GitOps on Kubernetes. With version 3.0, ApplicationSets, Argo Rollouts, and a growing ecosystem, the project addresses the requirements of modern platform teams: security, scalability, and developer productivity. Anyone investing in Kubernetes should seriously consider GitOps with Argo CD – the CNCF survey data speaks a clear language.

Sources

🌐 Machine-translated from the German original, editorially reviewed. 🤖 Written with AI assistance.