GitOps: yea or nay?
summary
Argues that putting the entire desired state in Git makes rollbacks trivial and agents enforce convergence; shows Flux on k3d bootstrapping to a two‑node cluster, syncing a repo that deploys namespace, backend and frontend with explicit dependsOn ordering, and the app comes up. Compares engines Argo CD, Flux and Jenkins X, and secret strategies sealed‑secrets, sops, Vault agent; explains pull‑based delivery (cluster polls Git), gives concrete CI flow: build image → update Git → cluster reconciles.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:00Small story
- 1:37Company disclosure
- 1:50Infrastructure as code
- 5:36Benefits
- 8:08Characteristics
- 9:29Flux
- 10:18ArgoCD
- 11:12Jenkins X
- 12:29Flux Demo
- 19:07Secrets
- 20:15GitOps vs Yak
- 20:57Push and pull
- 21:54Outro
