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

Enhancement: Automatically configure Kubernetes Image Puller with the list of images used by Codeready Workspaces

XMLWordPrintable

    • False
    • False
    • Hide
      = Configuring the default images for pre-pulling during {prod-short} installation using OperatorHub

      Before this release, using the Image Puller involved providing a list of images to pre-pull. With this release, when installed with {prod-short} using OperatorHub, the Image Puller auto-pulls the relevant images. The images to pre-pull are the default images used for workspace startup, including Theia, plugin broker, and sidecar images.
      Show
      = Configuring the default images for pre-pulling during {prod-short} installation using OperatorHub Before this release, using the Image Puller involved providing a list of images to pre-pull. With this release, when installed with {prod-short} using OperatorHub, the Image Puller auto-pulls the relevant images. The images to pre-pull are the default images used for workspace startup, including Theia, plugin broker, and sidecar images.

      https://github.com/eclipse/che/issues/19657 

      Is your enhancement related to a problem? Please describe.

      Today, using the KIPO requires manual configuration to add the list of images to pre-pull into your cluster, be it for offline/airgapped mode w/ OCP 3.11, or for performance tuning by caching the images across your cluster's various nodes.

      Describe the solution you'd like

      So, in future, it would be a great UX / simplification if the KIP could simply read the Che Operator's CSV and use that list of RELATED_IMAGE_* env vars to prepopulate the image list it will pull.

       

              dakwon@redhat.com David Kwon
              mmaler@redhat.com Michal Maléř
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: