Skip to main content

Argo CD Multi-Environment Repository Structure Checklist

How to organize your Git repositories when running Argo CD across dev, staging, and production. Covers folder layout, app-of-apps, ApplicationSets, secrets, RBAC, and promotion flow.

14items
Back to all checklists
GitOpsIntermediate

Argo CD Multi-Environment Repository Structure Checklist

How to organize your Git repositories when running Argo CD across dev, staging, and production. Covers folder layout, app-of-apps, ApplicationSets, secrets, RBAC, and promotion flow.

60-90 minutes
14 items
gitopsargocddeploymentsrepository-structurekubernetes
Progress0 / 14 completed
0%

Split application code from deployment manifests

Critical

Pick a base + overlay pattern (Kustomize or Helm)

Critical

Use the app-of-apps pattern as your entry point

Critical

Use ApplicationSet to fan out across environments

Pin production to a tag or branch, not HEAD

Critical

Define one AppProject per environment

Critical

Isolate environments by cluster or namespace

Critical

Automated sync for dev, gated for prod

Critical

Keep secrets out of Git, always

Critical

Promote with pull requests, not by editing prod folders directly

Critical

Lock down the config repo with branch protection

Critical

Set sync windows on the prod project

Wire up drift alerts and Slack notifications

Document the layout in a README at the repo root