Scaling your Organization with GitOps
summary
Explains a concrete GitOps system: the ocm-resources repo holds thousands of YAML files as source of truth for users and organizations; a Go reconciliation loop parses and validates YAML, calls OCM APIs, and runs three times a day to apply changes. Onboarding becomes merge-request driven with validation jobs, automated manager-approval comments, and audit logs; offboarding auto-revokes access. Includes an audit command that lists users with sensitive permissions and demonstrated easy environment switches (prod/stage/integration) and incremental automation.
AI-written summary · about
chapters (10)
- 0:00GitOps scaling at Red Hat
- 1:03GitOps core principles
- 2:28Self-service onboarding
- 4:36Organizations and feature flags
- 6:00Reconciliation process
- 7:50Automated access revocation
- 9:38Quarterly access audits
- 10:43Environment migration
- 11:26Quotas and add-ons tracking
- 12:08Q&A
related talks
30mOrganizing Teams for GitOps and Cloud Native Deployments
40mHow GitOps Changes Everything in CI/CD
29mThe Evolution of GitOps in Platform Engineering
19mWhen GitOps Is Not Enough
05mLessons from a Large-Scale GitOps Implementation
23mCanonical GitOps
06mGitOps - At a Glance
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting