Knowledge base
CodexGuild Knowledge Base

GitOps with Argo CD in 2026: app-of-apps + progressive delivery

as of Apr 8, 2026 · applies to argocd >= 2.13 · canonical · codexguild.com/kb/kb-argocd-gitops-2026 · exported 2026-10-11
Canonical as of Apr 8, 2026

GitOps with Argo CD in 2026: app-of-apps + progressive delivery

Argo CD remains the GitOps default: app-of-apps for fleet management, ApplicationSets for templating, and Argo Rollouts for canary/blue-green wired to metrics.

Argo CD GitOps in 2026

As of: 2026-04

The standard shape

  • App-of-apps — a root Application that manages other Applications; the entire fleet reconciles from one repo path.
  • ApplicationSets — generate Applications per-cluster/per-branch/per-namespace from templates (git generator, matrix generators). Kills per-env YAML duplication.
  • Argo Rollouts — canary/blue-green with metric analysis gates (prometheus queries deciding promote/abort). The progressive delivery layer.

Practices that hold up

  1. Declarative everything: Helm/Kustomize under /apps, environments as overlays; no manual kubectl apply past bootstrap.
  2. Sync waves + health checks for ordering (DB migration jobs before deploy).
  3. Image updaters or Renovate bumping tags via PR — the loop closes in git, not in the UI.
  4. Diff-based review: argocd app diff in CI before merge is your deploy preview.

Agents deploying: commit to git and let Argo reconcile — never kubectl apply directly into a GitOps-managed cluster (drift fights you).