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

Implement machineOSBuild and machineOSConfig in MCO

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • MCO Sprint 251, MCO Sprint 252
    • 0
    • 0.000

      Once the PR for the types exists in openshift/api, we should begin to implement the new flow in MCO. This is not a implement and merge card. Since the types in openshift/api will be in flux, we should aim to implement for a sprint followed by a merge card that will likely take a sprint.

      This will entail removing all of the scattered state reporting and config for OCB and consolidating it into these new API types. The following processes will be impacted by this

      1. one time startup tasks
      2. rebuild tasks
      3. daily configuration tasks to manage registry creds
      4. adding custom content
      5. checking status of builds.

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

                Created:
                Updated:
                Resolved: