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

Create enhancement and discuss the implementation of MachineConfigNode

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 5
    • False
    • None
    • False
    • OCPSTRAT-1845 - [GA]Disconnected Cluster Update and Boot without local image registry - phase 2
    • MCO Sprint 245, MCO Sprint 246, MCO Sprint 247, MCO Sprint 248, MCO Sprint 249, MCO Sprint 250
    • 0
    • 0.000

      It has been determined through API review that only upgrade health should live in the MachineConfigNode API type. However, the other progressions will live in the operator/v1 group under the machineconfiguration object.

      Given this design decision and the addition of the MCO API to openshift/api, we should create an enhancement for these changes and collaborate with openshift engineers to see who will be impacted by these changes

              cdoern@redhat.com Charles Doern
              cdoern@redhat.com Charles Doern
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: