Context:
 
We have two entry points for release payload:
1 - HostedCluster: dictates what runs in the management cluster and operators running in the guest cluster.
2 - NodePool: dictates the version of the ign payload, the OS machine content and so the kubelet version. If you were to use AWS/Kubevirt this would need to be in hand with you setting the right AMI/Image, as atm we default and hardcode to x86_64 https://github.com/openshift/hypershift/blob/c7c2b57c98caa518231c15eceefe62e98eece832/hypershift-operator/controllers/nodepool/nodepool_controller.go#L1323
 

DoD:

A NodePool user has the means in the NodePool API to specify the desired arch so the appropriate image can be found.

Implement it for AWS.

We have docs for running multi arch NodePools in https://hypershift-docs.netlify.app/.

We have an e2e running a NodePool within a different arch.