ArgoCD Architecture Overview
What You'll Learn
You'll understand the four core components that power ArgoCD's GitOps automation: the API server, repository server, application controller, and Redis.
The Four Pillars of ArgoCD
Think of ArgoCD as a restaurant kitchen: each component has a specific role, and they work together to deliver your desired state to Kubernetes.
API Server
The API server is ArgoCD's front door. It handles:
- The web UI and CLI requests
- Authentication and authorization
- Managing applications, projects, and settings
- Exposing the gRPC/REST API
It's like the restaurant host—taking orders and managing customer interactions.
Repository Server
The repository server is ArgoCD's connection to Git. It:
- Clones and monitors Git repositories
- Generates Kubernetes manifests (from Helm, Kustomize, YAML, etc.)
- Caches repository data for performance
- Handles credentials for private repos
Think of it as the recipe keeper—fetching and interpreting instructions from your cookbook (Git).
Application Controller
The application controller is the heart of GitOps reconciliation. It:
- Continuously monitors both Git (desired state) and Kubernetes (actual state)
- Detects drift between them
- Triggers sync operations to align actual state with desired state
- Manages application health status
This is your head chef—constantly checking that dishes match the recipe and fixing discrepancies.
Redis
Redis provides:
- Caching for improved performance
- Temporary storage for application state
- Message queue between components
It's the kitchen's communication board—keeping everyone coordinated and remembering important details.
How They Work Together
When you deploy an app, the API server receives your request, the repository server fetches manifests from Git, the application controller deploys to Kubernetes and monitors for drift, while Redis keeps everything fast and synchronized.
Key Takeaway: ArgoCD's architecture splits responsibilities across four components—API server for user interaction, repository server for Git operations, application controller for reconciliation, and Redis for coordination—enabling scalable, automated GitOps deployments.