Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-732

Support custom ignition configs at boot time

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 67% To Do, 0% In Progress, 33% Done
    • M
    • 0
    • Backlog Refinement

      Feature Overview (aka. Goal Summary)  

      Provide the bootstrap with specific instructions to execute through ignition configs by passing configuration options to the bootstrap node

      Goals (aka. expected user outcomes)

      Pass options via the install config manifest all the way to the bootstrap node by setting ignition config with the appropriate values

      Requirements (aka. Acceptance Criteria):

      • Users are able to pass options via the install config manifest
      • Provision in the bootkube to accept these flags and perform accordingly

      Background

      ARO requires specific settings such as network settings to be passed through the ignition configs at boot time. These configurations include things such as: important IPs for the image-registry that include all the mirrored OCP releases inside the Azure platform, etc. 

      Logging agent MDSD is also sent ignition config.

      Documentation Considerations

      This feature should be invisible to the OCP user.

      Implementation Considerations

      Terraform is used for all ignition booting (revisit after CAPZ)

              mak.redhat.com Marcos Entenza Garcia
              mak.redhat.com Marcos Entenza Garcia
              Jianwei Hou Jianwei Hou
              Stephanie Stout Stephanie Stout
              Patrick Dillon Patrick Dillon
              Marcos Entenza Garcia Marcos Entenza Garcia
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: