Epic Goal

• Create a report on the readiness of a cluster to migrate to include multi-arch compute nodes  based on compatibility between workload architecture and node architectures.

Why is this important?

• Users might want to be informed of the problems they might encounter or what characteristic their workloads have, before migrating to an actual multi-arch compute cluster.

Scenarios
1. As a user I want to find out how many of my deployments will get into a crashloopbackoff state because of the unavailability of the other architecture image

2. As a user I want to know what percentage of my workloads can fully support the move to a multi-arch compute cluster

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