How argoproj/argo-cd works
Argo CD is a declarative GitOps continuous-delivery platform for Kubernetes. A user defines or updates an Application through the UI, CLI, or API; the API persists the desired application configuration, the repo server obtains source content and generates manifests, and the application controller compares desired and live state and applies changes through the GitOps engine. ApplicationSets generate Applications from cluster, Git, pull-request, and other inputs; notifications, authentication, and cluster/repository management are additional product capabilities. The map reflects the provided tree, README, and sampled excerpts; some subsystem wiring is omitted where source excerpts do not establish it.
Main entry points: server.go API server · appcontroller.go Application controller · engine.go GitOps engine · types.go Application resources
Components 21
API and services
- API server
server/server.go - Application API
server/application/application.go - Session service
server/session/session.go
Desired state
- Application resources
pkg/apis/application/v1alpha1/types.go - Repo server
reposerver/server.go - ApplicationSet controller
applicationset/controllers/applicationset_controller.go - Application generators
applicationset/generators/interface.go
Reconciliation
- Application controller
controller/appcontroller.go - GitOps engine
gitops-engine/pkg/engine/engine.go - Cluster cache
gitops-engine/pkg/cache/cluster.go - Resource diff
gitops-engine/pkg/diff/diff.go - Sync executor
gitops-engine/pkg/sync/sync_context.go - Manifest hydrator
controller/hydrator/hydrator.go
Product extensions
- Notifications
notification_controller/controller/controller.go - Projects and policy
server/project/project.go - Settings service
server/settings/settings.go
Other components
- Operator
- Git repositories
- Kubernetes cluster
Connections 21
- Operator → Web UI: uses
- Operator → CLI: uses
- Web UI → API server: calls API
- CLI → API server: calls API
- API server → Application API: registers service
- API server → Session service: registers service
- Application API → Application resources: reads and writes
- Application resources → Application controller: triggers reconcile
- Application controller → Repo server: requests manifests
- Repo server → Git repositories: reads source
- Application controller → GitOps engine: syncs resources
- GitOps engine → Cluster cache: reads live state
- GitOps engine → Resource diff: compares resources
- GitOps engine → Sync executor: creates sync context
- Sync executor → Kubernetes cluster: applies resources
- ApplicationSet controller → Application generators: generates applications
- ApplicationSet controller → Application resources: creates and updates
- Application controller → Manifest hydrator: processes hydration
- Notifications → Application resources: observes applications
- Application API → Projects and policy: checks project policy
- API server → Settings service: initializes settings