Argo CD App of Apps with Helm: GitOps Repo Structure for Multiple Environments

In this video I build the GitOps repo structure I use on AKS: one Helm chart, per-environment values files, and an app-of-apps that creates every Argo CD Application from Git. Then I add a new environment live with a single commit, and show where ApplicationSets take over What you'll learn: A four-folder GitOps repo layout Why Argo CD recommends a config repo separate from your source code How per-environment Helm values work in Argo CD Building the app-of-apps pattern with Helm Where the root Application must point in a two-cluster setup Why app-of-apps gives you two reconciliation loops Adding a staging environment on camera with nothing but git push When to use app-of-apps vs ApplicationSets (and why most teams use both) ────────────────────────────────── TIMESTAMPS ────────────────────────────────── — 0:00 — Intro 1:14 — The problem with hand-made Applications 2:22 — The GitOps repo layout 5:55 — Overview of GitOps workflow 6:52 — Two reconciliation loops 7:30 — Demo: bootstrap and add staging with a commit 9:52 — Where ApplicationSets take over 11:08 — Outro ────────────────────────────────── CONNECT WITH ME: ────────────────────────────────── GitHub: [https://github.com/brayaON] Twitter/X: [https://x.com/brayaON20] LinkedIn: [  / bof23402  ] Website: [https://boflabs.dev/] ───────────────────────── TAGS: ───────────────────────── #argocd #gitops #kubernetes #azure #devops #cloudarchitecture