Running Multi-Arch Builds & Tests in OpenShift CI/CD
summary
CI/CD infrastructure runs across ~11 OpenShift clusters, executing ~5,000 jobs monthly and ~400,000 image builds; enabling multi-arch builds means orchestrating per-image builds, promotions and tests rather than a single toggle. The pipeline engine uses CI Operator and a modular step registry to resolve image dependency graphs, schedules per-arch OpenShift builds with node selector constraints, then constructs OCI manifest lists by calling the registry APIs to publish multi-architecture images and target tests to specific architectures.
AI-written summary · about
chapters (10)
- 0:00Multi-arch builds and tests intro
- 1:29OpenShift CI/CD overview
- 2:56CI operator role
- 4:22Step registry workflow
- 6:33Multi-arch dependency challenges
- 8:21Image promotion and management
- 10:09Test execution architecture control
- 12:38Multi-arch build process
- 13:43Architecture build pitfalls
- 14:27Portable scripts best practices
related talks
38mRunning Multi-Arch Builds & Tests in OpenShift CI/CD
42mCI/CD - Let The Robots Do Their Job!
47mContinuous Delivery Meets OpenShift
49mCI for OpenShift: Prow, ci-operator and the future
19mHow OpenShift Builds Container Images
22mOpenShift, or Kubernetes on steroids
25mCI/CD on OpenShift for developers
56m## Developer toolchain the cloud native way