Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-7958

Can Operator ImageProxy support "imageproxy:port/imagename:tag" in the image name?

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 2.10 GA
    • 3scale Operator
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Customer has reported APIManager resource does not seem to be able to handle "imageproxy:port/imagename:tag" in the image name, and assumes port is image tag.

      in the APIManager resource - they set the image name to use their image proxy - eg 
      spec.system.redisImage
      images.example.localdomain:5001/rhscl/redis-32-rhel7:latest

      Customer recieves the following error:
      "error":"DeploymentConfig.apps.openshift.io \"backend-redis\" is invalid: spec.template.labels: Invalid value: \"5001/rhscl/redis-32-rhel7:latest\"
      If customer attempts to workaround this by manually creating imagestreams, the operator overrides the system-memcache system-postgresql and zync-database imagestreams back to the original docker.io which is an issue as the customer is in a disconnected environment

       

      This is blocking the customer migrating to OCP4 - is there anything we can suggest?

            Unassigned Unassigned
            rhn-support-ahobson Aimi Hobson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: