Epic Goal

• Replace an x86 Control Plane and infra nodes with arm64 in running cluster. After the migration all e2e and tests should pass as they did before. Optionally, we should support arm64->x86 migrations.

Why is this important?

• Customers want to save money by replacing x86 control plan and infra nodes with arm without having to rebuild their cluster(s).

Scenarios

1. migrate x86 control plane to arm
2. migrate x86 infra nodes to arm
3. migrate both x86 control plane and infra nodes to arm
4. migrate arm control plane to x86
5. migrate arm infra nodes to x86
6. migrate both arm control plane and infra nodes to x86

Acceptance Criteria (for the above scenarios)

• all e2e/confromance tests should pass post-migration
• during the migration, all e2e/conformance tests should pass
• Validate that image stream behavior pre, post and during migration is consistant.

Dependencies (internal and external)
1. There will be manual steps to ensure that all imagestreams are set to 'preserve original'

Previous Work (Optional):
1. …

Open questions::
1. unclear what the cluster's stability will be during migration( 1 arm, 2 x86 cp nodes)
2.

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