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

Implement consistent reporting of paused resources in Cluster API

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • CLOUD Sprint 251, CLOUD Sprint 252, CLOUD Sprint 253, CLOUD Sprint 254, CLOUD Sprint 255, CLOUD Sprint 256, CLOUD Sprint 257, CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261, CLOUD Sprint 263, CLOUD Sprint 264, CLOUD Sprint 262, CLOUD Sprint 265

      Background

      https://github.com/kubernetes-sigs/cluster-api/issues/10130 describes a scenario in which all controllers in Cluster API report their paused status via conditions.

      This condition will be used as part of the handover mechanism between Machine API and Cluster API versions of resources.

      Steps

      • Identify pause-able resources upstream, Clusters, MachineDeployments, MachineSets, Machines et al
      • Implement in each controller a pause condition that identifies when the resource is paused, or not.

      Stakeholders

      • Cluster Infra
      • Upstream CAPI

      Definition of Done

      • Upstream resources report paused via a condition that acknowledges that they have been paused.
      • Docs
      • <Add docs requirements for this card>
      • Testing
      • <Explain testing that will be added>

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

                Created:
                Updated:
                Resolved: