Epic Goal

• The goal of this epic is to enable operator teams to run their verification tests on multi-arch clusters by ensuring there are clusters with multi-arch compute nodes available in the pre-provisioned PROW ClusterClaims pool.
• Since this enables testing across a wide variety of operators, this goal of this changes is to work with QE to ensure that these new clusters are used with a wide variety of operators once they become available.

Why is this important?

• This is important because pre-provisioned clusters is a huge part of how QE tests existing operators. By include multi-arch clusters in the pool of claimable test environments, we can find issues with operators without specifically have to evaluate each operator individually.

Scenarios
1. …

Acceptance Criteria

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

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