It's 2030. What Does Prow Look Like?
summary
Prow runs owners-file enforcement and automated reviewer assignment across 90+ Kubernetes repos, interprets who can give LGTM or approve, triggers and executes CI by spawning pods, and merges via Tide when tests and approvals pass. Major gaps: poor integration with GitHub merge queues and Actions, no native pipeline DAGs (Tekton handles pipelines better), mounting security and maintenance burden as contributions fall since 2020. Practical futures: Tide merge queue interoperability, delegating pipelines to Tekton, and a spawn pod CI model with a lightweight hosted/packaged distribution.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:07What Prow is
- 7:24Why Prow was ahead
- 9:56World since Prow's start
- 13:27Security and CI challenges
- 15:12Prow's current state
- 19:33Future possibilities
- 20:17Core functions to keep
- 22:04GitHub dependency
- 23:49Moving from GitHub
- 25:14Prow's Kubernetes impact
- 25:57Prow as a product
- 26:41Prow for non-K8s projects
- 28:08Migrating to modern CI
- 29:14Prow vs GitHub Actions
- 30:39Future directions
- 32:48Prow alternatives
- 34:10Conclusion and Q&A
related talks
36mSIG Testing Deep Dive
20mBuilding, Managing and Automating Clusters at Scale With Prow
46mKubernetes native CI/CD with Prow
36mIntro: SIG Testing
36mModern CI/CD with Tekton and Prow Automated via Jenkins X
49mCI for OpenShift: Prow, ci-operator and the future
29mCloud Native CD Pipelines with Tekton
42mCI/CD - Let The Robots Do Their Job!