Kubernetes native CI/CD with Prow
summary
Kubernetes/OpenShift-native CI/CD built with Prow, with configs stored in ConfigMaps and Secrets and jobs running in a separate test namespace; deployment uses the command-line installer tackle (defaults to a 3‑node cluster, ~4 CPUs/8GB each). Core components: plank executes jobs with decorator sidecars that decorate uploads artifacts to GCS, tide manages retesting and merging with label/approval rules, sinker garbage‑collects old pods, and crier posts Slack notifications. Example setup shows ~53 jobs, repo-based job folders, automatic configmap updates from a config repo, and working auto-merge on PRs.
AI-written summary · about
chapters (30)
- 0:00Intro
- 2:44namespaces
- 3:27services
- 4:22decorate
- 6:29deck
- 6:50PR Status
- 7:06Author History
- 8:01Sinker
- 10:28Notification
- 11:40Deploying
- 13:40Summary
- 14:28Any questions
- 17:02Configuration
- 19:10Config
- 23:19Plugin
- 25:05Build Configuration
- 26:25PR
- 28:03Plugin Configuration
- 29:48Config Maps
- 31:08Progress Owner Labels
- 32:18Filters
- 33:17Reviewers
- 36:49Job config
- 37:46Manual config
- 37:57Testing
- 39:38PR Configuration
- 40:17PR Summit
- 41:02Notifications
- 41:49General secret
- 42:45Questions
related talks
20mBuilding, Managing and Automating Clusters at Scale With Prow
36mSIG Testing Deep Dive
36mIntro: SIG Testing
49mCI for OpenShift: Prow, ci-operator and the future
33mDeep Dive: Prow
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow
34mIt's 2030. What Does Prow Look Like?
39mKubernetes-centric CI/CD