Uploaded image for project: 'OpenShift Pod Autoscaling'
  1. OpenShift Pod Autoscaling
  2. PODAUTO-202

Switch PODAUTO builder to use openshift/release image instead of ocp/builder

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • PODAUTO - Sprint 257

      Currently, several of our projects are using registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.17 (or other versions of images from that family) as part of their build.

      This image has more tooling in it and is more closely aligned with what is used for building shipping images:

      registry.ci.openshift.org/openshift/release:rhel-9-release-golang-1.22-openshift-4.17

      As an OpenShift developer, I would like to use the same builder images across our team's builds where possible to reduce confusion. Please change all non-UBI builds to use the openshift/release image instead of the ocp/builder image in these repos:
      https://github.com/openshift/vertical-pod-autoscaler-operator

      https://github.com/openshift/kubernetes-autoscaler (VPA images only)

      https://github.com/openshift/cluster-resource-override-admission-operator

      https://github.com/openshift/cluster-resource-override-admission

      Also update the main branch to match images of any CI builds that are changed:

      https://github.com/openshift/release

       

       

            rh-ee-macao Max Cao
            joelsmith.redhat Joel Smith
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: