Epic Goal

• Define the -multi image in the clusterImageSet
• Enable the -multi image to be used by RHACM cluster create flow

Why is this important?

• Customers would like to be able to use ACM to deploy different OCP architecture types than the hub architecture.
• This is what we refer to as 'cross architecture' deployment: eg, hub on x86, deploy OCP on Arm

Scenarios

1. From x86 hub, use the cluster create flow to deploy Arm cluster
2. OCP Image version selection should offer OCP 4.12+ with -multi arch image
3. Arch type can be selected and this will update all aspects of the install-config yaml appropriately
   1. We need to consider that when Arch type gets selected, we perhaps offer different sets of image types. eg, when AWS cloud and arm64 platform is used, offer AWS m6g types

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Verify the existing doc topic is updated to make use of -multi image

Dependencies (internal and external)

1. OCP 4.12 -multi arch image support: https://coreos.slack.com/archives/CJARLA942/p1662681270363779?thread_ts=1662657509.954889&cid=CJARLA942
   1. #multi-arch channel would probably be in charge, or at least aware of, communication efforts

Previous Work (Optional):

1. ACM-1057
2. https://github.com/stolostron/acm-hive-openshift-releases/pull/51

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>