Argo CD 3.0: safer GitOps with lower memory use

2025-05-06 · Publisher : Argo CD · Domain : Cloud & DevOps

On 6 May 2025, Argo CD 3.0 is released, a month after the first release candidate was presented at KubeCon Europe in London: stronger log authorizations, revised defaults and better performance.

### Background On 6 May 2025, version **3.0.0** of Argo CD, the CNCF's GitOps continuous delivery tool, is released. The CNCF had presented the first release candidate on 1 April 2025 at KubeCon + CloudNativeCon Europe in London, with general availability announced for early May. The stated goal: more performance, scalability and security. ### Key facts - Security: RBAC authorization on logs is enforced by default, and fine-grained rights inheritance is disabled by default. - Performance: batch event processing is enabled by default and application health is stored in Redis by default. - SPDY is replaced by WebSocket for port forwarding and pod exec. - Updated dependencies: Helm 3.17.0 and kubectl 1.32.1; better Azure workload identity support for Git and OCI repositories. - Previously optional but widely used settings become defaults; several changes are breaking, for example the `compareOptions` defaults. ### Why it matters Argo CD is one of the most widespread continuous deployment tools on Kubernetes. A major version requires migration work: changes in default behavior (log RBAC, rights inheritance, comparisons) can block teams or pipelines if not anticipated. For an IT services firm running Argo CD at clients, version 3 calls for an audit of existing settings before upgrading. Contributions come notably from Akuity, BlackRock, Intuit, Octopus Deploy, Pipekit and Red Hat, according to the CNCF announcement. ### Takeaway Argo CD 3.0 tightens defaults on security and performance, at the price of breaking changes to prepare for.

Tags : CI/CD, Kubernetes, DevOps, Open Source, Cloud natif