Peribolos: GitHub Management Amidst Growth in Kubernetes Project!
summary
Peribolos enforces GitHub org state from a YAML repo of declared orgs and teams, reconciling 9 orgs, 370+ repos, 670+ teams and ~2,000 members by inviting, promoting or removing accounts automatically. Workflow: edit kubernetes-sigs config, merge PR, prow job runs Peribolos which diffs declared vs actual and applies changes when run with confirm. Built-in safety includes minimum five admins checks and dry-run mode; it now manages team→repo permissions, exported orgs with export to YAML, and is CI-agnostic though commonly runs on prow.
AI-written summary · about
chapters (18)
- 0:00Welcome
- 1:08Peribolos for growth
- 3:37Manual GitHub pain points
- 5:06What Peribolos is
- 7:39Peribolos in Kubernetes
- 9:26Membership with Peribolos
- 11:32Peribolos and Prow
- 13:46Safety checks in Peribolos
- 15:13Peribolos in action
- 16:40Peribolos adaptations
- 17:43Team repo permissions
- 18:26Peribolos design
- 19:08Adoption impact
- 20:12Q&A
- 20:32Token permissions
- 21:57Team hierarchy support
- 23:08Reconciliation loop
- 24:13Peribolos future
related talks
28mPeribolos: How Kubernetes Uses GitOps to Manage GitHub Communities at Scale
34mIt's 2030. What Does Prow Look Like?
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
20mBuilding, Managing and Automating Clusters at Scale With Prow
36mIntro: SIG Testing
36mSIG Testing Deep Dive
36mWhale Care 101 - How We Organize A 200+ Devs Project
35mGitOps - Operations by Pull Request