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

Investigate if MCN API updates are needed to represent OCL's current and desired image values

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • MCO Sprint 272
    • 0

      In a standard node update, the desired and current node config versions are represented in the `machineconfiguration.openshift.io/desiredConfig` and `machineconfiguration.openshift.io/currentConfig` node annotation values. With the introduction of OnClusterLaying (OCL), two node annotations, `machineconfiguration.openshift.io/currentImage` and `machineconfiguration.openshift.io/desiredImage`, were added to represent the desired and current image states of a node. This spike aims to help us understand if the image states should be represented in the MachineConfigNode (MCN) resource and, if so, where.

      Done when:

      • There is an understanding on whether we want to include image state information in the MCN resource and, if so, where it should live.
        • This decision should be documented.
      • The description for MCO-1675 is updated with information on the API updates needed as a result of this investigation work.

      References:

      • The reference in the OCL enhancement describing the image state annotations can be found here.

              rh-ee-ijanssen Isabella Janssen
              rh-ee-ijanssen Isabella Janssen
              Naseerah Kani Pakrudeen Ali (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: