Argo CD — Overview#

Identity#

Purpose#

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. It automates the deployment and lifecycle management of applications by continuously reconciling the desired state declared in Git with the actual state running in a Kubernetes cluster. It targets platform engineers and DevOps teams running applications on Kubernetes who want auditable, version-controlled deployments without imperative pipelines.

Significance#

Argo CD is a CNCF graduated project and one of the most widely adopted GitOps tools in the Kubernetes ecosystem. It has a massive user base spanning enterprises (IBM, Red Hat, Intuit, NVIDIA) and startups alike, and it effectively popularized the GitOps delivery model. Its influence extends to shaping the GitOps specification and spawning companion tools (Argo Rollouts, Argo Workflows, Argo Events). The SLSA Level 3 badge and CII Best Practices certification reflect its maturity in security and supply-chain posture.

Key metrics#

  • Go files: 975 (excluding vendor)
  • Top-level directories: applicationset, cmd, cmpserver, commitserver, common, controller, docs, gitops-engine, hack, manifests, notification_controller, notifications_catalog, overrides, pkg, reposerver, resource_customizations, server, test, tools, ui, util
  • Direct dependencies: ~138 (from go.mod, excluding // indirect)
  • Indirect dependencies: 186 marked // indirect in go.mod
  • First commit / age: Initial public release circa 2018; version 3 module path indicates major evolution

Notable characteristics#

  • Multi-binary architecture: Distinct binaries for the API server (server), application controller (controller), repo server (reposerver), commit server (commitserver), and CMP server (cmpserver) — each with distinct responsibilities and security boundaries.
  • Config Management Plugin (CMP) system: A first-class plugin interface allowing arbitrary tooling (Helm, Kustomize, Jsonnet, custom generators) to be used as config sources, making the system highly extensible without forking.
  • gitops-engine sub-module: The sync and diff engine is factored into a sub-module (gitops-engine/), enabling shared infrastructure with other CNCF tools and reflecting deliberate modularity.
  • Kubernetes-native design: Heavy use of Kubernetes CRDs (Application, AppProject, ApplicationSet) means Argo CD extends the Kubernetes API rather than building its own resource model, enabling use of existing RBAC, GitOps tooling, and kubectl.
  • Casbin RBAC + OIDC: Uses Casbin for fine-grained policy enforcement alongside OIDC/OAuth2 integration, reflecting the enterprise security requirements of its target audience.
Backward Istio — Testing Argo CD — Structure Forward