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

Create / manage custom build pod via BuildController


    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 8
    • False
    • None
    • False
    • OCPSTRAT-35 - Layering ON Cluster Build: Dev Preview
    • 0
    • 0.0

      This is intended to create our own custom build pod via BuildController which will be used as a fallback if the OpenShift Build API is unavailable. The productionized BuildController will use the interface discussed in MCO-563 to interface with this new custom build pod implementation. As a first-pass, we can use the OS image since it has Podman on it.

      A future consideration (out-of-scope for this card) is using a dedicated Buildah image (e.g., quay.io/buildah/stable:latest), which should be versioned and managed via the OpenShift release manifest mechanism.


      Done When:

      • The productionized BuildController has a drop-in way to use custom build pods instead of the OpenShift Build API.
      • We may want to expose a knob that will let us explicitly select this custom build pod for testing purposes, though we can later remove it.

            zzlotnik@redhat.com Zack Zlotnik
            zzlotnik@redhat.com Zack Zlotnik
            0 Vote for this issue
            1 Start watching this issue