GitOps with Argo CD
The GitOps principles, installing Argo CD, your first Application, sync policies, self-healing, drift, and structuring the config repo per environment.
Stage 0 was push-based: a human (or CI job) runs a command that changes servers. GitOps flips it. A controller inside the Kubernetes cluster continuously compares the cluster with a Git repository and makes the cluster match. Deploys become pull requests, rollbacks become `git revert`, and nobody needs cluster credentials in CI.
+ ShopLite gains: a shoplite-gitops config repo, Argo CD managing ShopLite in dev and prod, with automated sync, self-heal, and per-environment overlays
- 1.1
GitOps Principles and Installing Argo CD
A local Kubernetes cluster running Argo CD, and a clear picture of why pull-based delivery beats `kubectl apply` from CI.
35 minFree — local kind cluster1 break-its - 1.2
Your First Application: Sync and Health
ShopLite's web Deployment and Service deployed by Argo CD from Git, with a deploy done purely by a commit.
40 minFree2 break-its - 1.3
Automated Sync, Self-Heal, Pruning, and Sync Waves
Argo CD deploys every merge automatically, reverts manual cluster edits, deletes what's removed from Git, and applies resources in the right order.
40 minFree2 break-its - 1.4
Environments, Overlays, and the CI → Git Handoff
Dev and prod from one base using Kustomize overlays, a Helm-sourced dependency, CI that bumps image tags by commit, and an app-of-apps root.
60 minFree2 break-its