Panel Discussion: GitOps & Best Practices for Cloud Native CI/CD
summary
Defines GitOps as operation by pull request with Git as the single source of truth, driving Kubernetes/Terraform orchestration and CI like Jenkins and Jenkins X. Claims atomic, convergent updates with easy rollback and an audit log that eliminates hero fixes; team velocity jumps from infrequent releases toward 100 deployments per week in examples. Emphasizes increased observability, automated alerts, and a demo recovery where a blown-away cluster is restored from Git within minutes.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:30Configuration as Code
- 2:27Git Ops
- 3:52Git as a Pattern
- 5:30Biggest Challenge
- 5:58Why GitOps
- 9:32Cultural Impact
- 11:45People are hard
- 14:23Reliability
- 16:14Psychological Safety
- 17:53Audience Questions
related talks
05mCloud Native CI/CD using 'GitOps'
45mGitops: The Kubernetes way
55mGitOps, Fostering Next-Generation Operations Teams
47mGitOps - Using Git as your source of truth for build, deploy and observability
35mGitOps - the holy grail of devops
26mKeynote Session: GitOps as an Evolution of Kubernetes
40mHow GitOps Changes Everything in CI/CD
34mGitOps Is Likely More Than You Think It Is