← DevOps tools
Tool / Kubernetes

ArgoCD

A declarative, GitOps continuous delivery tool for Kubernetes. It watches the desired state stored in Git and reconciles a cluster until it matches.

Why it exists.

It solves deployment drift and the uncertainty of manual releases by making Git the auditable source of truth for what should run in a cluster.

Where it shines.

Kubernetes applications that need repeatable, observable, multi-environment delivery with pull-request-based change control.

Where not to use it.

Do not use it as a general-purpose CI runner, for non-Kubernetes workloads, or when the team is not ready to treat Git changes as production changes.

What it is made of.

  • Application controller
  • API server and UI
  • Repository and cluster credentials
  • Git repository containing desired state

How it works.

  1. A change is committed to Git
  2. ArgoCD detects the new desired state
  3. The controller compares Git with the cluster
  4. ArgoCD syncs resources and reports health
Questions and answers.Open the interview practice set for ArgoCD.
Search