Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1010

Builds Operator Deploys Upstream Images

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • builds-1.1
    • Openshift-Builds-1.0.2
    • builds-operator
    • None
    • False
    • None
    • False
    • Builds Sprint #9, Builds Sprint #10
    • Customer Facing
    • Approved

      Description of problem:

      After installing Builds for OpenShift 1.0.2, the operator deploys operands that have upstream container images.

      Workaround: None

      Prerequisites (if any, like setup, operators/versions):

      • OpenShift 4.16
      • OperatorHub deploying Builds for OpenShift 1.0.2

      Steps to Reproduce

      1. Deploy a 4.16 cluster
      2. Install OpenShift Pipelines
      3. Install Builds for OpenShift 1.0.2
      4. Create `ShipwrightBuild` instance (following instructions). 

      Actual results:

      After creating the `ShipwrightBuild` instance, the operator deploys operand images from upstream resources.

      Expected results:

      Operands only deploy images from the Red Hat Container Catalog

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      Operator only deploys operands from the Red Hat container catalog (or other official source).

      Definition of Done:

      Build Details:

      Builds for OpenShift 1.0.2

      Additional info (Such as Logs, Screenshots, etc):

       

              jitensingh Jitendar Singh
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: