← All insightsProduction

Running Argo CD in production: a hardening checklist

CodeWizard Engineering · 21 June 2026 · 3 min read · Advanced

Demos and production are different sports. This checklist covers what changes when Argo CD has to be reliable, secure and observable under real load.

Security and reliability defaults

  • Scope Argo CD RBAC per project and team
  • Encrypt secrets (SOPS/Sealed Secrets) rather than committing plaintext

A production-minded config

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]

Operational best practices

  • 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
In production, boring and reproducible beats clever every time.

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