Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-23275

Container images must properly set the url label

XMLWordPrintable

    • Container images must properly set the url label
    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do

      Epic Goal

      All of the ACM and MCE container images should define the url label.  

      Today if I look at the url label I see a generic value "https://www.redhat.com", for example:
      skopeo inspect --no-tags docker://registry.redhat.io/rhacm2/console-rhel9@sha256:d4c42a203110050a3834be8d5a0eee384ad7e9fbb991da589d75acd15055b8b1 | jq .Labels.url
      "https://www.redhat.com"

      We want that value to look like:
      "https://github.com/stolostron/console"

      It is important to know which repository was used to build our images.  Especially for some cases like kube-rbac-proxy which exists in our stolostron org but also exists in the openshift org.  

      Why is this important?

      See above

      Scenarios

      ...

      Acceptance Criteria

      ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions:

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub
        Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.
      • Considerations were made for Extended Update Support (EUS)

              gparvin-redhat Gus Parvin
              gparvin-redhat Gus Parvin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: