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

[ spike ] MachineConfig fields we can't push into ignition or rpm-ostree origin.d api?

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • U (215)
    • 0

      Fields under consideration: 

      • extensions (already pushed into rpm-ostree origin.d) 
      • fips
      • kernelArguments
      • kernelType
      • osImageURL

       

      Questions:

      1. Aside from the obvious osImageURL, are there any MachineConfig fields that we can't use a combination of rpm-ostree and ignition-liveapply to apply to our image?
      2. If there are any, how are we going to get them applied to the image?

              mkenigsb@redhat.com Matthew Kenigsberg (Inactive)
              jkyros@redhat.com John Kyros
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: