Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2685

Productize the must-gather and host images on registry.redhat.io

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • 1.9.0
    • None
    • None
    • None
    • 8
    • False
    • None
    • False
    • GITOPS Sprint 232, GITOPS Sprint 237, GITOPS Sprint 238

      Story (Required)

      As a user of the gitops must-gather, I want to use a secure image hosted on registry.redhat.io 

      Background (Required)

      The official images of custom must-gathers should be hosted on registry.redhat.io instead of quay.io. 

      Other must-gathers use the format registry.redhat.io/openshift-gitops-1/gitops-must-gather-rhel-8:[version_tag] so we should too even though the underlying image will be the same for all tags (since the must-gather is agnostic of version). This is a request of the must-gather team that we do it this way for consistency. __ 

      Approach (Required)

      Have someone with the correct build/push an image based on the must-gather and push it to registry.redhat.io with the following tags:

      • registry.redhat.io/openshift-gitops-1/gitops-must-gather-rhel-8:v1.9

      Acceptance Criteria (Mandatory)

      Have all images with tags for supported gitops operator versions listed on registry.redhat.io so that a user of the must gather can run: 

      oc adm must-gather --image=registry.redhat.io/openshift-gitops-1/gitops-must-gather-rhel-8:[gitops-operator-version]

       

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            rescott1 Regina Scott
            rescott1 Regina Scott
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: