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

Spike on achieving parity with MCO node disruption frequency

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • MCO Sprint 267
    • 0

      Skip ignition-apply in OCL by default, in order to aid rollbacks to non-OCL & keep architectural alignment 

       

      This is more than just removing the the RUN command that executes the ignition apply process and the ostree commit after.

      The difficult part with removing Ignition Apply is will be getting the events set up correctly. For example: If someone wants to install a new extension or an alternative kernel, we want to do a build in that situation. However, if they're rolling a new MachineConfig for updating SSH keys, we want to ignore that situation and just apply it to a live system.

       

      Done when:

      • Complete POC that can validate proposed solution
      • Write out implementation tasks

              dkhater@redhat.com Dalia Khater
              mkrejci-1 Michelle Krejci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: