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

Merge API types for v1alpha1/MachineConfigNode

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • 5
    • False
    • None
    • False
    • OCPSTRAT-845 - [Tech Preview] Proper MCO State Reporting
    • MCO Sprint 244
    • 0
    • 0.000

      Creating and Merging the API task are two separate tasks.

      Creating the types involves design review, meetings and discussions.

      In the case of the MachineStateController's API types the design went through the following major changes

       

      1) MachineState – Upgrade+Component Progression + event based system

      2) MachineState – Upgrade+ Component Progression + non event based system

      3) MachineConfigState – Upgrade (per pool) based on Nodes + non event based system

      4) MachineConfigNode – Upgrade, one object per node, conforms to k8s API and openshift api conventions.

      5) MachineConfigNode (same as above) + MachineConfiguration – tracks operator progression and lives in a different API group final and current design

      Given these changes which took roughly 1.5 sprints to figure out, the merging of these types is going to be set aside as a separate task which will undergo more review.

              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: