[FEATURE]: SHIP-0043 Multi-arch Image Builds

[adambkaplan]

Feature Tracker

This is a higher level "feature tracker" for an approved enhancement proposal. Each discrete task to implement the feature should have its own child issue, linked to an appropriate Shipwright repository.

SHIP-0043: Multi-arch Image Builds

Overview

SHIP-0043 proposes adding support for building multi-architecture container images in Shipwright. Multi-arch builds require executing individual image builds in parallel and/or on different nodes, which cannot be efficiently accomplished in a single Pod/TaskRun without emulation or cross-compilation. The implementation requires refactoring the BuildRun controller to use PipelineRuns instead of TaskRuns, enabling parallel execution of architecture-specific builds.

Goals

• Enable building container images for multiple architectures (e.g., amd64, arm64, s390x, ppc64le)
• Support parallel execution of architecture-specific builds
• Allow builds to execute on nodes with matching architectures
• Provide a foundation for future execution backends (e.g., Argo Workflows)

Related Issues

The following existing issues are part of the implementation plan for multi-arch builds:

• shipwright-io/build#1968: [FEATURE] Use PipelineRuns for Builds (experimental) - This issue tracks the foundational refactoring work needed to support PipelineRuns, which is a prerequisite for multi-arch builds.

Child Issues

• shipwright-io/build#2075: Implement multi-arch build API, orchestration, and node selection
• shipwright-io/build#2076: Create manifest index for multi-arch images
• shipwright-io/website#197: Document multi-arch build feature
• shipwright-io/website#198: Add multi-arch build examples and tutorials
• shipwright-io/website#199: Update API reference documentation

---

Generated-by: Cursor