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

[Enhancement] Openshift Layering Integration (Design)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.12
    • None
    • OCP CoreOS Layering - MCO
    • False
    • False
    • Green
    • In Progress
    • OCPSTRAT-143 - Allow admins to add 3rd party and custom content to RHCOS
    • Impediment
    • OCPSTRAT-143Allow admins to add 3rd party and custom content to RHCOS
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Minimal goal: minimal design decision (and enhancement) for the interface for the hotfix workflow; describe general goal of user experience

      First Enhancement: https://github.com/openshift/enhancements/pull/1032

      Stretch: Have a concrete plan that has been approved by team

      • Figure out the optimal path for support to troubleshoot with all these additional inputs and layers
      • Treat Machine Config as a UX
      • Determine impact on support and derive requirements from those experiences (goal would be to reduce the friction that customers have tripped over in the past)
      • Decide on format of layers in machine configs
      • Get 2 specific use cases/layer candidates that we want to try to support
      • Disaster recovery workflows - https://github.com/ostreedev/ostree-rs-ext/issues/121#issuecomment-1005211976 (I didn’t want this to get lost / forgotten in the ether)

          1.
          		 Docs tracker Sub-task Closed Undefined Unassigned

              rhn-engineering-skumari Sinny Kumari
              mkrejci-1 Michelle Krejci
              Mrunal Patel
              Rio Liu Rio Liu
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: