Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1029

Pull in changes for the opt-in API into the MCO

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 8
    • True
    • Depends on API changes by MCO-678
    • False
    • OCPSTRAT-1170 - Updated boot images: Phase 2 (GCP GA, AWS TP)
    • MCO Sprint 251, MCO Sprint 252
    • 0
    • 0.000

      This is the MCO side of the changes. Once the API PR lands, the MSBIC should start watching for the new API object. 

      It is also important to note that MachineSets having an ownerreference should not opted in to this mechanism, even if they are opt-ed in via the API. See discussion here: https://github.com/openshift/enhancements/pull/1496#discussion_r1463386593

      Done when:

      • user has a way to switch update mechanism on and off
      • MachineSets with an OwnerRef are ignored.

       

      Update 3/26/24 - Moved ValidatingAdmissionPolicy bit into a separate story as that got a bit more involved.

              djoshy David Joshy
              djoshy David Joshy
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: