Epic Goal

The goal of this Epic is to provide support for Heterogeneous (multi-arch) builds for Builds Classic (aka Builds v1). Given that OpenShift supports multi-arch clusters, BuildConfigs should be able to build an image for a specific architecture available in the cluster and schedule the builder pods to a node with the specified architecture, and update a multi-arch manifest list accordingly.

Why is this important?

With the enablement of OpenShift clusters with mixed architecture capable compute nodes it is necessary to have support for manifest listed images so the correct images/binaries can be pulled onto the relevant nodes. 

Scenarios

1. ...

Acceptance Criteria

• BuildConfigs can build images for a specified architecture on a worker node of matching architecture
• BuildConfigs can update a multi-arch manifest list with the image built for the specified architecture
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

Reference material

• Podman: Working with container image manifest lists

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>