Running Multi-Arch Builds & Tests in OpenShift CI/CD
summary
Operates a CI/CD platform across 11 OpenShift clusters with ~100,000 job definitions and ~500,000 daily executions; implements PROW + CI Operator plus a custom job dispatcher that labels jobs by capabilities to route ARM64 work to clusters with ARM nodes. Builds run per-architecture using nodeSelectors, produce two images then create an OCI manifest list for promotion; solution works but exposes broken Dockerfiles and scripts, increases build graph complexity, and requires organizational changes to avoid defaulting to AMD64.
AI-written summary · about
chapters (8)
- 0:00Multi-arch CI/CD intro
- 6:33CI Operator workflow engine
- 13:26Job dispatcher clusters
- 16:20Image dependencies in CI
- 19:58Architecture in image builds
- 23:56Step-level arch control
- 30:21Debugging build failures
- 34:35Key takeaways
related talks
15mRunning Multi-Arch Builds & Tests in OpenShift CI/CD
13mOptimizing Workload Management in a Multi-Cluster Environment: A Case Study
42mCI/CD - Let The Robots Do Their Job!
49mCI for OpenShift: Prow, ci-operator and the future
16mMulti-Arch FedoraCI container builds with OKD
34mScheduling in CI/CD systems
44mPerformance and Scalability Tuning Kubernetes for OpenShift and Docker
47mContinuous Delivery Meets OpenShift