← All posts
ArgoCDKubernetesGitOps

GitOps with ArgoCD: lessons from production

App-of-apps, sync waves and the small conventions that keep a GitOps repo calm.

GitOps sounds simple: the cluster should look like the repo. In practice a few conventions make the difference between calm and chaos.

App of apps

A single root Application points at a folder of child Applications — one per service and environment. Adding a service is a pull request, nothing more.

Sync waves for ordering

CRDs and namespaces go first, then operators, then workloads. Annotating resources with sync waves removed a whole class of "works on the second sync" problems.

Keep secrets out of git

We reference secrets from AWS Secrets Manager through the External Secrets Operator, so the repo stays safe to share with the whole team.

  • Separate config repo from application code
  • Auto-sync in dev, manual promotion in production
  • Alerts on OutOfSync and Degraded states