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

have the MCS still generate ignition configs with certs

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • 8
    • False
    • None
    • False
    • TELCOSTRAT-87 - Single Core CPU CaaS Budget for DU Deployment w/ Single-Node OpenShift on Sapphire Rapids Platform
    • MCO Sprint 239, MCO Sprint 240
    • 0
    • 0.000

      although we are removing the config from the machineconfig, ignition (both in bootstrap and in-cluster) need to generate ignition with the certs still, so nodes can join the cluster

       

      We will need the incluster MCS to read from controllerconfig, and bootstrap MCS (during install time) to be able to remove it from the machineconfigs to ensure no drift when master nodes comes up

              cdoern@redhat.com Charles Doern
              jerzhang@redhat.com Yu Qi Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: