Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3379

Image puller operator kube-rbac-proxy should not be pulled from gcr.io

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      = Kubernetes Image Puller air gap support

      The images required to run the Kubernetes Image Puller are now all published in the same container registry (quay.io) and can be easily mirrored in a customer OpenShift cluster.
      Show
      = Kubernetes Image Puller air gap support The images required to run the Kubernetes Image Puller are now all published in the same container registry (quay.io) and can be easily mirrored in a customer OpenShift cluster.
    • Enhancement

      Image puller operator Pod includes a kube-rbac-proxy container (c.f. the screenshot) that gets pulled from gcr.io.

      In some restricted networks where OpenShift is deployed, containers from gcr.io are blacklisted and the image puller operator cannot be installed.

      Possible solutions are:

      • Use the the same kube-rbac-proxy image used by devspaces (i.e. quay.io/brancz/kube-rbac-proxy:v0.11.0)
      • Allow the images to be configurable from the CheCluster CR

        1. image-puller-rbac-proxy.png
          image-puller-rbac-proxy.png
          531 kB
        2. Kubernetes_Image_Puller_Operator_1.0.3__ds_3.2.0.RC-10-14.png
          Kubernetes_Image_Puller_Operator_1.0.3__ds_3.2.0.RC-10-14.png
          150 kB
        3. screenshot-1.png
          screenshot-1.png
          29 kB

              dakwon@redhat.com David Kwon
              mloriedo Mario Loriedo
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: