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

Default the Authoritative API from spec to status for MAPI Machines/MachineSets on Creation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • CLOUD Sprint 273

      Background

       

      To prevent concurrent reconciles from the capi, mapi, machine_sync and machine_migration controllers while the .status.AuthoritativeAPI is empty, we need to propagate the .spec.authoritativeAPI value to the .status.authoritativeAPI if it is empty/not set.

      Context: https://redhat-internal.slack.com/archives/GE2HQ9QP4/p1747044925443129?thread_ts=1745998127.382269&cid=GE2HQ9QP4 

      Steps

      • Determine if we can use MAP (Mutating Admission Policy) (We can't)
      • Implement behaviours for MAPI creation as per above description.
      •  

      Stakeholders

      • Cluster Infra
      •  

      Definition of Done

      • When creating a MAPI resource that has an empty .status.authoritativeAPI, above rules on defaulting are observed
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

              ddonati@redhat.com Damiano Donati
              ddonati@redhat.com Damiano Donati
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: