Automation and the Kubernetes Contributor Experience - Aaron Crickenberger, Samsung SDS
summary
Automation replaces sprawling Jenkins with a Kubernetes-native stack using prow, gubernator, mungegithub, and testgrid to run CI at scale. Infrastructure runs 4.3 million jobs in a year with about 600,000 tied to PRs, retires the build‑cop role, and moves from 100–150 Jenkins nodes to pods on clusters. PRs merge by batching (over 50% tested as batch testing), labels and OWNERS files drive reviewer/approver selection, and bots handle lifecycle, retest and triage chores.
AI-written summary · about
chapters (5)
related talks
43mTransformative Culture
24mUnlocking CI Performance in the Age of Agentic Development
57mRise of the Machines - Automate Your Development
30mIntro: Kubernetes Contributor Experience SIG
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
37mGitHub Actions + K8S to level up software dev
36mDeveloper Productivity On a Budget
19mHow to utilize Open Source tools to create CI/CD & DevOps workflows
