GitOps for the People
summary
MoneyBank migrates to OpenShift + GitOps but delivery remains slow because handoffs and compliance gates are manual. Engineers build a ticket-driven ReleaseOps flow: issue status changes trigger Jenkins pipelines that build images, push to Artifactory/Nexus, update per-environment config repos, run automated tests and reconcile clusters, which cuts production errors and enables daily deployments in greenfield apps. Final regulatory production approval stays manual, so the system reduces toil but keeps a guarded human gate.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 2:15Money Bank case study overview
- 7:14What is GitOps?
- 10:57Automating the release process
- 16:43Results and speed improvements
- 19:18Introducing Release Notes
- 23:25Architecture and cost savings
- 24:12Impact of COVID and future outlook
- 25:21Platform engineering insights
- 26:20Closing and Q&A
related talks
34mGitOps for the people
35mGitOps - Operations by Pull Request
40mHow GitOps Changes Everything in CI/CD
55mGitOps, Fostering Next-Generation Operations Teams
06mGitOps - At a Glance
19mCrossing the Divide: How GitOps Brought AppDev & Platform Teams Together!
47mGitOps - Using Git as your source of truth for build, deploy and observability
30mThe Intersection of CD Gates and GitOps: A Match Made in Deployment Heaven