-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
8
-
None
-
CLOUD Sprint 277, CLOUD Sprint 278
Background
For the Machine sync controller, we need to implement logic for converting the MachineAPI Machine ProviderStatus to ClusterAPI AWSMachine status and vice versa.
This will involve adding provider specific logic in the conversion packages and in the sync controller to add status details from the authoritative resource to the non-authoritative resource
This card covers the case for both directions.
Steps
- Implement MAPI to CAPI conversion by leveraging library for conversion, beware of the differences between core CAPI v1beta1 status and v1beta2 status changes
- Reach out to other implemented providers (Openstack? IBMCloud/PowerVS?) and ask them how that's going to be looking like for them/ask for planning for implementing it.
Stakeholders
- Cluster Infra
Definition of Done
- When a Machine exists, the non-authoritative Machine counterpart's status is kept up to date if there are changes
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- clones
-
OCPCLOUD-2995 Implement Machine status conversion during syncing
-
- Closed
-
- links to