← All insightsConcepts

Argo CD: core concepts and configuration explained

CodeWizard Academy · 23 June 2026 · 3 min read · Beginner

GitOps continuous delivery for Kubernetes - Git is the source of truth, the cluster is reconciled to match. This walkthrough covers the mental model and the configuration you will actually touch.

Argo CD is a Kubernetes controller that continuously compares the live cluster to manifests in Git and syncs any drift, giving you declarative, auditable, self-healing deployments.

The configuration that matters

An Application that tracks a Git path and self-heals.

yaml
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata: { name: web, namespace: argocd }
spec:
  project: default
  source:
    repoURL: https://github.com/acme/deploy.git
    targetRevision: main
    path: apps/web
  destination:
    server: https://kubernetes.default.svc
    namespace: web
  syncPolicy:
    automated: { prune: true, selfHeal: true }
    syncOptions: [CreateNamespace=true]

Principles to hold onto

  • Adopt app-of-apps to manage many Applications declaratively
  • Enable selfHeal + prune so the cluster always matches Git
  • Use Sealed Secrets/SOPS so secrets can live safely in Git

Everyday commands

bash
argocd app sync web
argocd app get web
argocd app history web
argocd app rollback web 3

Want senior help putting Argo CD to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult