How GitOps Changes Everything in CI/CD
summary
A large German industrial migration cuts release cycles from 6–12 months toward daily deploys by switching to a repo-driven deployment loop that stores Kubernetes YAML and Helm charts in Git, uses a sync controller to apply them, and adds pipelines that build images and push to registries. Demonstrated tooling includes ArgoCD, Flux and Jenkins X; it works for automation and security but creates repo sprawl, weaker deploy feedback, and registry-to-Git drift.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:00What is GitOps
- 7:59CI/CD fundamentals
- 12:07GitOps in CI/CD
- 16:56Company-wide GitOps
- 24:38GitOps tools
- 30:10GitOps implementation example
- 31:59GitOps challenges
- 37:03Q&A
related talks
47mGitOps - Using Git as your source of truth for build, deploy and observability
45mGitops: The Kubernetes way
07mIntroduction to GitOps
06mGitOps - At a Glance
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
09mThe Future of GitOps in Modern DevOps
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven
46mGitOps, Jenkins X & the Future of CI/CD