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

Add Paused condition to Machine and MachineSet resources

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • CLOUD Sprint 253, CLOUD Sprint 254, CLOUD Sprint 255, CLOUD Sprint 256, CLOUD Sprint 257, CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260

      Background

      When the Machine and MachineSet MAPI resource are non-authoritative, the Machine and MachineSet controllers should observe this condition and should exit, pausing the reconciliation.

      When they pause, they should acknowledge this pause by adding a paused condition to the status and ensuring it is set to true.

      Behaviours

      • Should not reconcile when .status.authoritativeAPI is not MachineAPI
      • Except when it is empty (prior to defaulting migration webhook)

      Steps

      • Ensure MAO has new API fields vendored
      • Add checks in Machine/MachineSet for authoritative API in status not Machine API
      • When not machine API, set paused condition == true, otherwise paused == false (same as CAPI)
        • Condition should be giving reasons for both false and true
      • This feature must be gated on the ClusterAPIMigration feature gate

      Stakeholders

      • Cluster Infra

      Definition of Done

      • When the status of Machine indicates that the Machine API is not authoritative, the Paused condition should be set and no action should be taken.
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

            rh-ee-tbarberb Theo Barber-Bany
            joelspeed Joel Speed
            Milind Yadav Milind Yadav
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: