Epic Goal

• To validate the multiarch-tuning-operator can work on Hypershift (managed and management clusters
• To validate the multiarch-tuning-operator can work on Hypershift-based managed offerings

Why is this important?

• Enable seamless use of the multiarch payload by default in several scenarios (managed services, rosa hcp, hypershift management clusters with mixarch workers when they handle single-arch hosted clusters)
• https://issues.redhat.com/browse/HOSTEDCP-1902

Scenarios
1. [hypershift management cluster] handle single-arch amd64 and single-arch arm64 managed clusters from the same management cluster
2. [hypershift managed cluster with mixarch nodepools] same scenario as the classic one for OCP (user-wide)

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