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

Automate pushing development OCI RHCOS container images

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 0
    • 0

      Currently, new OCI base images for RHCOS are not automatically built and pushed into OpenShift, unlike their ostree-native counterparts.

      To facilitate this, we can make use of the pre-existing Jenkins jobs for RHCOS which handle the ostree-native versions, amongst other things. There's already some prior art in the form of a merged PR (https://github.com/coreos/fedora-coreos-pipeline/pull/457) to the FCOS pipeline repository. An equivalent PR should be made to the RHCOS pipeline repository (https://gitlab.cee.redhat.com/coreos/redhat-coreos) as well.

       

      Done When:

      • The destination container registry is determined.
      • What access controls the above container registry should have, including push secrets for us to use. (Stretch: Do we need to consider Red Hat subscriptions for registry access?)
      • The RHCOS pipeline is modified to enable automated container pushes to the above container registry.

              zzlotnik@redhat.com Zack Zlotnik
              zzlotnik@redhat.com Zack Zlotnik
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: