Epic Goal

• Deliver multi-arch improvements to Shipwright, a lot of which is outlined here:
  • https://github.com/shipwright-io/community/issues/213
  • https://github.com/shipwright-io/community/blob/main/ships/0039-build-scheduler-opts.md
  • https://github.com/shipwright-io/build/issues/1119 

Why is this important?

• This makes it easier to use shipwright in a multi-arch compute environment by adding features such as NodeSelectors and Tolerations that didn't previously exist. 

Scenarios
1. …

Acceptance Criteria

• (Enter a list of Acceptance Criteria unique to the Epic)
• …

Dependencies (internal and external)
1. …

Previous Work (Optional):
1. continuation of shipwright work done in https://issues.redhat.com/browse/MULTIARCH-4665

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'.