-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
-
OCPSTRAT-854 - Support Heterogeneous NodePools Within HyperShift
-
-
-
Hypershift Sprint 250, Hypershift Sprint 251, Hypershift Sprint 252, Hypershift Sprint 253, Hypershift Sprint 254
-
0
-
0
-
0
User Story:
As a user of the HyperShift CLI, I would like the CLI to fail early if these conditions are all true:
- the release image is not multi-arch
- the management cluster's CPU architecture is not the same as the NodePool's CPU architecture
so that we can prevent a HostedCluster from being created that will have errors due mismatches between the release image, management cluster's CPU architecture, and NodePool's CPU architecture.
Acceptance Criteria:
- The HyperShift CLI fails to create a cluster when the release image is not multi-arch and the management cluster's CPU architecture does not match the NodePool's CPU architecture.
- There is documentation providing information the CLI will fail when it meets the conditions above.
(optional) Out of Scope:
This should be done for the API as well but will be covered thru HOSTEDCP-1105.
Engineering Details:
- HyperShift CLI currently defaults to a multi-arch image in version.go.
This requires/does not require a design proposal.
This requires/does not require a feature gate.
- is cloned by
-
HOSTEDCP-1105 Warn the user in the API if the release image is not multi-arch and the management cluster's CPU architecture is not the same as the NodePool's CPU architecture
- Closed
- links to