-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
BU Product Work
-
False
-
False
-
OCPSTRAT-532 - HyperShift support for ROKS
-
Undefined
-
-
Hypershift Sprint 2
-
0
-
0
-
0
Context:
We rely on MCO run (an ephemeral pod, as if it was a library) in bootstrap mode to render ignition configs out of an input.
At the moment hypershift nodes are labeled as "master" because multiple operators manifests are scheduled to a master pool.
DoD:
MCO support rendering for worker pool in bootstrap mode.
Hypershift nodes are not labeled as "master"
- is related to
-
OCPSTRAT-326 Implement HyperShift Infrastructure & Machine Management Models
- Closed
-
OCPSTRAT-520 Hypershift support for Managed Services (ROSA, ARO, OSD,...)
- Closed