-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
Define UX and failures for HC with multi-arch NodePools.
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-854 - Support Heterogeneous NodePools Within HyperShift
-
OCPSTRAT-854Support Heterogeneous NodePools Within HyperShift
-
0% To Do, 0% In Progress, 100% Done
-
0
-
0
-
0
User Story:
Using a multi-arch Node requires the HC to be multi arch as well. This is an good to recipe to let users shoot on their foot. We need to automate the required input via CLI to multi-arch NodePool to work, e.g. on HC creation enabling a multi-arch flag which sets the right release image
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.
- is cloned by
-
HOSTEDCP-1220 Define UX and failures for HC with multi-arch NodePools.
- Closed