-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
3
-
None
-
None
-
CLOUD Sprint 261, CLOUD Sprint 263, CLOUD Sprint 264, CLOUD Sprint 262, CLOUD Sprint 265, CLOUD Sprint 266, CLOUD Sprint 267
Background
For the Machine controller, we need to implement a forward conversion, converting the MachineAPI Machine to ClusterAPI.
This will involve creating the CAPI Machine if it does not exist, and managing the Infrastructure Machine.
This card covers the case where MAPI is currently authoritative.
Behaviours
- Create Cluster API mirror if not present
- CAPI mirror should be paused on create
- Names of mirror should be 1:1 with original
- Manage InfraMachine creation by converting MAPI providerSpec
- InfraMachine should be named based on the name of the Machine (to mirror CAPI behaviour)
- InfraMachine should have appropriate owner references and finalizers created
- Ensure CAPI Machine spec and status overwritten with conversion from MAPI
- Ensure Labels/Annotations copied from MAPI to CAPI
- On failures
- Set Synchronized condition to False and report error on MAPI resource
- On success
- Set Synchronized condition to True on MAPI resource
- Set status.synchronizedGeneration to match the auth resource generation
Steps
- Implement behaviours described above to convert MAPI Machines to CAPI Machines using conversion library
Stakeholders
- Cluster Infra
Definition of Done
- MAPI Machines create paused CAPI mirrors
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- is depended on by
-
OCPCLOUD-2716 [Core] Handle Machine owner references translation between MAPI and CAPI
-
- Closed
-
- links to