When Git Push Meets Human Pushback: The Culture of GitOpS
summary
A GitOps rollout in a messy hybrid environment causes a one‑day recovery after deleted staging secrets and several rogue kubectl incidents, so the team implements branch protection, moves approvals into ArgoCD + GitHub Actions with policy as code, and adds Prometheus/Grafana monitoring and developer‑friendly pipeline logs. Clear ownership comes from simple repo owners files and an owners.md per repo, a phased path for prod only, and a Python SDK so developers can work in their language rather than learning YAML.
AI-written summary · about
chapters (7)
- 0:00GitOps introduction
- 6:03Overcoming pushback
- 10:39Escaping gatekeeping
- 13:50Trust via feedback
- 16:45Redesigning processes
- 19:55From enforcement to ownership
- 22:25From resistance to shared love for GitOps
related talks
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
35mGitOps - the holy grail of devops
35mGitOps - Operations by Pull Request
34mStop clicking and start committing: a GitOps workflow for endpoint management
30mThe Objectives And The Principles Behind GitOps
40mHow GitOps Changes Everything in CI/CD
55mGitOps, Fostering Next-Generation Operations Teams