GitOps for the people
summary
200-engineer fintech with siloed QA, divergent dev/stage/prod stacks, and an approvals bottleneck moves to Kubernetes/OpenShift plus mandatory automated tests, Jenkins pipelines that copy manifests into a config repo, and Argo CD doing the sync. Release branches go away; delivery ties to Jira issues in a new Release Ops flow where Ops approves a PR to the prod config repo and ArgoCD deploys automatically. Result: fewer production surprises, embedded testers, revert-commit rollback lane with human sign-off.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 2:17Company discovery and challenges
- 7:12Initial GitOps proposal
- 10:42Original delivery pipeline
- 13:10Automating the release manager role
- 17:07Production deployment with approvals
- 19:13Identifying remaining bottlenecks
- 21:20Introducing ReleaseOps concept
- 24:07Final GitOps architecture
- 26:36Internal developer platforms
- 27:19Demo of Loft platform
- 28:44Q&A session
related talks
27mGitOps for the People
35mGitOps - the holy grail of devops
35mGitOps - Operations by Pull Request
43mGitOps at Scale with and Argo CD on
47mGitOps - Using Git as your source of truth for build, deploy and observability
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
