Epic Goal

• Install a cluster in Azure with different cpu architectures for the control plane and workers.

Why is this important?

Scenarios
1. …

Acceptance Criteria

• Install a cluster with an x86 control plane arm workers
• Install a cluster with an arm control plane x86 workers
• Validate that the installer can support the above configurations (ie fails gracefully with single arch payload)
• Provide a way for the user to know that their installer can support multi-arch installs.(ie openshift-install version)

Dependencies (internal and external)
1. It would be cleaner to implement if/when we adopt marketplace: https://issues.redhat.com/browse/SPSTRAT-271

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