-
Spike
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
-
OCPSTRAT-1579 - Integrate Cluster API (CAPI) in standalone OCP-Phase 3
-
-
-
CLOUD Sprint 264
Once we have CAPI as the backend for MAPI and CAPI machines, we have the ability to switch to using bootstrap data requests, via a minimal bootstrap provider.
The bootstrap provider could be responsible for creating a small ignition stub, pointing out to the MCS endpoint, but, adding some additional context such as per node bootstrap secrets or IPAM configuration.
We would like to understand:
- How would changing to per node bootstrap data be accomplished, what is the migration story?
- What are the benefits, and how would things like per node bootstrap credentials work today? Does this allow for a reduced reliance on cluster-machine-approver?
- Where do we have customers requesting per node configuration today? Potentially baremetal and other IPAM related cases
CC decarr who had some thoughts about this during the CAPI F2F in July '24