GitOps: yea or nay?
summary
Claim: GitOps makes Kubernetes deployments reproducible, auditable and faster and reduces MTTR by keeping desired state in Git. Demo uses Flux bootstrapped into a k3d cluster to deploy a podinfo app via kustomize, installing source/helm/customize/notification controllers, committing and reconciling manifests, and verifying a working service via port‑forward and metrics endpoint. Mentions alternatives ArgoCD, Flux and Jenkins X, and secrets options like sealed‑secrets or Vault agent sidecar injector. No surprising metrics are given.
AI-written summary · about
chapters (10)
- 0:00GitOps for reliability
- 1:17What is GitOps
- 3:45GitOps benefits
- 9:01GitOps agents in Kubernetes
- 10:03GitOps tools: Flux vs Argo vs Jenkins X
- 13:11Flux live demo
- 19:35Secrets and security in GitOps
- 20:39GitOps versus Infrastructure as Code
- 21:45Push vs pull models
- 22:27Summary
related talks
26mGitOps: yea or nay?
23mGitOps: yea or nay?
31mGitOps and Kubernetes: a Winning Combo
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
15mGitOps Use Cases & Best Practices Com...
45mGitops: The Kubernetes way
47mGitOps - Using Git as your source of truth for build, deploy and observability
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes