Epic Goal

• Identify and work to resolve all gaps to support multiarch payloads

Why is this important?

• So that all architectures are fully supported and usable by default.

Assumptions:

• BuildsV1 will eventually go away
• BuildsV2 Built on Shipwright is the likely future via an installable operator
• Konflux will continue to be the designated future path, but could possible used Shipwright
• The solution priority from Product is:

1. 1. Konflux/RHTAP (but most of this work is undertaken by others outside our team)
   2. Customer builds
   3. CI builds

• Argo workflows underpin BuildsV1
• Tekton is a service that requires connectivity (unsure of this)

Scenarios
1. Users of OCP can easily build and use multiarch containers

2. Internally, OCP containers are built to be multiarch aware

3. Tooling supports multiarch containers in an intuitive way

Acceptance Criteria

• Tooling just works for multiarch containers
• Deployments of heterogeneous clusters just work, whether these are day 0 or day 1 or day 2 operations

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.