GitOps: yea or nay?
summary
Argues that storing the entire desired state in Git makes cluster recovery and rollbacks trivial, demonstrates Flux bootstrapping a k3d cluster, reading a kustomize-based repo, applying manifests and committing state back to Git to keep cluster and repo in sync. Compares agents ArgoCD, Flux and Jenkins X, explains pull model for security vs push pipelines, shows secrets options (Bitnami Sealed Secrets and Mozilla SOPS) and a live deploy of podinfo to prove automation and self-healing.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:23Disaster recovery with GitOps
- 3:10GitOps core principles
- 7:23Benefits of GitOps
- 9:08GitOps software agents overview
- 10:50Flux and Argo CD explained
- 13:17Jenkins X and GitOps
- 14:00GitOps pipeline workflow
- 15:25Live demo of Flux
- 22:26Handling secrets in GitOps
- 23:29GitOps vs Infrastructure as Code
- 23:51Push vs pull in GitOps
- 24:53Security and multi-cloud benefits
- 25:14Q&A and resources
related talks
23mGitOps: yea or nay?
23mGitOps: yea or nay?
35mGitOps - the holy grail of devops
31mGitOps and Kubernetes: a Winning Combo
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
15mGitOps Use Cases & Best Practices Com...
47mGitOps - Using Git as your source of truth for build, deploy and observability
24mHosting Applications in the Real World