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

Bootstrap MCO should parse MOSC yamls

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • MCO Sprint 278, MCO Sprint 279, MCO Sprint 280
    • 0
    • 0

      When OCL is enabled at install time, the bootstrap MCO should be able to parse MOSC yamls to build the image(s) for the nodes.

      • There should be 2 MOSC, one for master nodes and one for worker nodes
      • If OCL is enabled in install-config.yaml but an MOSC is not provided by the user, generate a basic one for the installation
        • this can be done in the future, for now we can fail if the user doesn't create a MOSC yaml
      • A registry is needed on the boostrap node to hold the image built for the master nodes
      • Once master nodes are up with a base version of RHCOS, run rpm-ostree rebase or bootc switch to boot the nodes into the image that was built

       

      Note: the bootstrap node cannot communicate with worker nodes. It will only be responsible for building and serving content for the control-plane/master nodes. While implementing, verify that this is actually the behavior of the bootstrap node.

              umohnani Urvashi Mohnani
              umohnani Urvashi Mohnani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: