Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2999

Implement AWS InfraMachine/Provider status conversion during syncing

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • 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>

              rh-ee-cschlott Christian Schlotter
              ddonati@redhat.com Damiano Donati
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: