SIG Testing Deep Dive
summary
Prow replaces a fragile Jenkins setup by representing CI jobs as a custom resource and running them as Kubernetes pods so upgrades no longer kill in‑flight work. Components are Hook, Plank, Horologium, and plugins; integrations include Kubetest, Gubernator, Boskos and TestGrid. Production scale is real: about 181 Prow nodes, ~3.4 million jobs last year, ~770 job configs and resubmits for 31 repos. Merge automation uses Tide with batching (currently size five) and a single deployment merges PRs across dozens of repos.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:52What is prowl
- 1:58Why build another system
- 2:59Why test Kubernetes
- 4:10Kubernetes Pro
- 5:29How Proud Works
- 11:56Kubernetes
- 14:37Conflicting PRs
- 15:40Serial Testing
- 17:04Submit Queue Problems
- 22:29Sen Lu Improvements
- 24:30Roadmap
- 27:32Plugin Testing
- 32:07Dashboards
related talks
36mIntro: SIG Testing
20mBuilding, Managing and Automating Clusters at Scale With Prow
46mKubernetes native CI/CD with Prow
35mIntro: Testing SIG
49mCI for OpenShift: Prow, ci-operator and the future
34mIt's 2030. What Does Prow Look Like?
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow
42mSIG Testing: Intro And Updates