Language:
Format:

Chapter 8. Caching images for faster workspace start

To improve the start time performance of CodeReady Workspaces workspaces, use the Image Puller. The Image Puller is an additional OpenShift deployment. It creates a DaemonSet downloading and running the relevant container images on each node. These images are already available when a CodeReady Workspaces workspace starts.

The Image Puller provides the following parameters for configuration.

Table 8.1. Image Puller parameters

Parameter	Usage	Default
`CACHING_INTERVAL_HOURS`	DaemonSets health checks interval in hours	`"1"`
`CACHING_MEMORY_REQUEST`	The memory request for each cached image when the puller is running. See Section 8.2, “Defining the memory parameters for the Image Puller”.	`10Mi`
`CACHING_MEMORY_LIMIT`	The memory limit for each cached image when the puller is running. See Section 8.2, “Defining the memory parameters for the Image Puller”.	`20Mi`
`CACHING_CPU_REQUEST`	The processor request for each cached image when the puller is running	`.05` or 50 millicores
`CACHING_CPU_LIMIT`	The processor limit for each cached image when the puller is running	`.2` or 200 millicores
`DAEMONSET_NAME`	Name of DaemonSet to create	`kubernetes-image-puller`
`DEPLOYMENT_NAME`	Name of the Deployment to create	`kubernetes-image-puller`
`NAMESPACE`	OpenShift project containing DaemonSet to create	`k8s-image-puller`
`IMAGES`	Semicolon separated list of images to pull, in the format `<name1>=<image1>;<name2>=<image2>` See Section 8.1, “Defining the list of images to pull”.
`NODE_SELECTOR`	Node selector to apply to the Pods created by the DaemonSet	`'{}'`
`AFFINITY`	Affinity applied to pods created by the DaemonSet	`'{}'`
`IMAGE_PULL_SECRETS`	List of image pull secrets, in the format `pullsecret1;…` to add to pods created by the DaemonSet. Those secrets need to be in the image puller’s namespace and a cluster administrator must create them.	`""`

Additional resources

8.1. Defining the list of images to pull

Prerequisites

The curl tool is available. See curl homepage.
The jq tool is available. See jq homepage.
The yq tool is available. See yq homepage.

Procedure

Get the list of relevant container images.

Example 8.1. Getting the list of all images for CodeReady Workspaces 2.9

$ curl -sSLo- https://raw.githubusercontent.com/redhat-developer/codeready-workspaces-images/crw-2.9-rhel-8/codeready-workspaces-operator-metadata-generated/manifests/codeready-workspaces.csv.yaml \
  | yq -r '.spec.relatedImages[]'

Retain the images involved on the workspace startup phase:
- eap
- machineexec
- mongodb
- pluginbroker
- plugin-
- stacks
- theia
- ubi-minimal

Exclude from the list the container images not supported by the target platform.

For AMD64 and Intel 64 (x86_64), exclude openj9 images.

Example 8.2. Image list for AMD64 and Intel 64 (x86_64), excluding openj9 images

che_workspace_plugin_broker_artifacts=registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:c0a096ed1829b21b0641d98c591139324affc0c866a5e011ae6627dd22d316c6;
che_workspace_plugin_broker_metadata=registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986;
codeready_workspaces_machineexec=registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:7bc2f046c1fcb00ab7656de7a7c31da73e71af3164314f77960061102f44c9da;
codeready_workspaces_plugin_java11=registry.redhat.io/codeready-workspaces/plugin-java11-rhel8@sha256:e86be19ea5c4868f68188a46cec3f4131c1a18400f6800b27d5da92c95c2418b;
codeready_workspaces_plugin_java8=registry.redhat.io/codeready-workspaces/plugin-java8-rhel8@sha256:bb8ec9c4964e39b335be589f027c4b5ec866fe5f742c7181473e70fff717655d;
codeready_workspaces_plugin_kubernetes=registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8@sha256:f40c6cf67df5294f5d767312633a5ce5cf8b542f660f52f3252c61d6c5342f9e;
codeready_workspaces_plugin_openshift=registry.redhat.io/codeready-workspaces/plugin-openshift-rhel8@sha256:a8f9e97a6946bbd5e0ac515621408cb361531bc33c99983f17aaf547a44776a2;
codeready_workspaces_stacks_cpp=registry.redhat.io/codeready-workspaces/stacks-cpp-rhel8@sha256:8855029f8658060e79513bd51bad33e38134adf0586286ef2a02bdf27e9dd526;
codeready_workspaces_stacks_dotnet=registry.redhat.io/codeready-workspaces/stacks-dotnet-rhel8@sha256:0422cfa23c5eefdda978bbec4f1fc2c24fccfa5a9568d5bda69e3232efefec54;
codeready_workspaces_stacks_golang=registry.redhat.io/codeready-workspaces/stacks-golang-rhel8@sha256:de9daf2d87903ebabf03f64e4c15d6f4f7106525396f31bad555ce858864219c;
codeready_workspaces_stacks_php=registry.redhat.io/codeready-workspaces/stacks-php-rhel8@sha256:59c41da505474c48617cec3759064db55bab69bf8cd6f9752bfa95b8756dc710;
codeready_workspaces_theia=registry.redhat.io/codeready-workspaces/theia-rhel8@sha256:925be51cad7d93eae735039cd76569ef14bdf546876584479a5b037758defc7b;
codeready_workspaces_theia_endpoint=registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:42cd00002085280c39534ad856df6adac925218be07ee652b78d92c24cf71573;
jboss_eap_7_eap73_openjdk8_openshift_rhel7=registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7@sha256:d16cfe30eaf20a157cd5d5980a6c34f3fcbcfd2fd225e670a0138d81007dd919;
jboss_eap_7_eap_xp2_openjdk11_openshift=registry.redhat.io/jboss-eap-7/eap-xp2-openjdk11-openshift-rhel8@sha256:647d092383a760edc083eafb2d7bc3208d6409097281bedbd5eaccde360e7e39;
pvc_jobs=registry.redhat.io/ubi8/ubi-minimal@sha256:2f6b88c037c0503da7704bccd3fc73cb76324101af39ad28f16460e7bce98324;
rhscl_mongodb_36_rhel7=registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73;

For IBM Z and IBM Power Systems, use openj9 version for java8 and java11, and exclude dotnet.

Example 8.3. Image list for IBM Z and IBM Power Systems: using openj9 version for java8 and java11, and excluding dotnet

che_workspace_plugin_broker_artifacts=registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:c0a096ed1829b21b0641d98c591139324affc0c866a5e011ae6627dd22d316c6;
che_workspace_plugin_broker_metadata=registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986;
codeready_workspaces_machineexec=registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:7bc2f046c1fcb00ab7656de7a7c31da73e71af3164314f77960061102f44c9da;
codeready_workspaces_plugin_java11_openj9=registry.redhat.io/codeready-workspaces/plugin-java11-openj9-rhel8@sha256:3fa85acf846cf774276bd243e58eaaf3ff26cc53e2fbaf69ad336ef8a054e741;
codeready_workspaces_plugin_java8_openj9=registry.redhat.io/codeready-workspaces/plugin-java8-openj9-rhel8@sha256:2593b8602800de8e0713cf31708fec8c68dcb0d92f8da770ebe89d9310c04e6a;
codeready_workspaces_plugin_kubernetes=registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8@sha256:f40c6cf67df5294f5d767312633a5ce5cf8b542f660f52f3252c61d6c5342f9e;
codeready_workspaces_plugin_openshift=registry.redhat.io/codeready-workspaces/plugin-openshift-rhel8@sha256:a8f9e97a6946bbd5e0ac515621408cb361531bc33c99983f17aaf547a44776a2;
codeready_workspaces_stacks_cpp=registry.redhat.io/codeready-workspaces/stacks-cpp-rhel8@sha256:8855029f8658060e79513bd51bad33e38134adf0586286ef2a02bdf27e9dd526;
codeready_workspaces_stacks_golang=registry.redhat.io/codeready-workspaces/stacks-golang-rhel8@sha256:de9daf2d87903ebabf03f64e4c15d6f4f7106525396f31bad555ce858864219c;
codeready_workspaces_stacks_php=registry.redhat.io/codeready-workspaces/stacks-php-rhel8@sha256:59c41da505474c48617cec3759064db55bab69bf8cd6f9752bfa95b8756dc710;
codeready_workspaces_theia=registry.redhat.io/codeready-workspaces/theia-rhel8@sha256:925be51cad7d93eae735039cd76569ef14bdf546876584479a5b037758defc7b;
codeready_workspaces_theia_endpoint=registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:42cd00002085280c39534ad856df6adac925218be07ee652b78d92c24cf71573;
jboss_eap_7_eap73_openjdk8_openshift_rhel7=registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7@sha256:d16cfe30eaf20a157cd5d5980a6c34f3fcbcfd2fd225e670a0138d81007dd919;
jboss_eap_7_eap_xp2_openj9_11_openshift=registry.redhat.io/jboss-eap-7/eap-xp2-openj9-11-openshift-rhel8@sha256:7cdfbf16587dd8688f26595df43c8c30e069625997581e898368203cb059c88b;
jboss_eap_7_eap_xp2_openjdk11_openshift=registry.redhat.io/jboss-eap-7/eap-xp2-openjdk11-openshift-rhel8@sha256:647d092383a760edc083eafb2d7bc3208d6409097281bedbd5eaccde360e7e39;
pvc_jobs=registry.redhat.io/ubi8/ubi-minimal@sha256:2f6b88c037c0503da7704bccd3fc73cb76324101af39ad28f16460e7bce98324;
rhscl_mongodb_36_rhel7=registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73;

Exclude from the list the container images mounting volumes in Dockerfile.

Additional resources

8.2. Defining the memory parameters for the Image Puller

Define the memory requests and limits parameters to ensure pulled containers and the platform have enough memory to run.

Prerequisites

Section 8.1, “Defining the list of images to pull”

Procedure

To define the minimal value for CACHING_MEMORY_REQUEST or CACHING_MEMORY_LIMIT, consider the necessary amount of memory required to run each of the container images to pull.
To define the maximal value for CACHING_MEMORY_REQUEST or CACHING_MEMORY_LIMIT, consider the total memory allocated to the DaemonSet Pods in the cluster:
```
(memory limit) * (number of images) * (number of nodes in the cluster)
```
Pulling 5 images on 20 nodes, with a container memory limit of 20Mi requires 2000Mi of memory.

Additional resources

8.3. Installing Image Puller using the CodeReady Workspaces Operator

This section describes how to use the CodeReady Workspaces Operator to install the Image Puller. This is a Community-supported technology preview feature.

Prerequisites

Section 8.1, “Defining the list of images to pull”
Section 8.2, “Defining the memory parameters for the Image Puller”
Operator Lifecycle Manager and OperatorHub are available on the OpenShift instance. OpenShift provides them starting with version 4.2.
The CodeReady Workspaces Operator is available. See Installing CodeReady Workspaces on OpenShift 4 using OperatorHub

Procedure

Edit the CheCluster Custom Resource and set .spec.imagePuller.enable to true
Example 8.4. Enabling Image Puller in the CheCluster Custom Resource
```
apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: codeready-workspaces
spec:
  # ...
  imagePuller:
    enable: true
```
Uninstalling Image Puller using CodeReady Workspaces Operator
- Edit the CheCluster Custom Resource and set .spec.imagePuller.enable to false.

Edit the CheCluster Custom Resource and set the .spec.imagePuller.spec to configure the optional Image Puller parameters for the CodeReady Workspaces Operator.

Example 8.5. Configuring Image Puller in the CheCluster Custom Resource

apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  name: codeready-workspaces
spec:
  ...
  imagePuller:
    enable: true
    spec:
        configMapName: <kubernetes-image-puller>
        daemonsetName: <kubernetes-image-puller>
        deploymentName: <kubernetes-image-puller>
        images: 'che_workspace_plugin_broker_artifacts=registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:c0a096ed1829b21b0641d98c591139324affc0c866a5e011ae6627dd22d316c6;che_workspace_plugin_broker_metadata=registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986;codeready_workspaces_machineexec=registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:7bc2f046c1fcb00ab7656de7a7c31da73e71af3164314f77960061102f44c9da;codeready_workspaces_plugin_java11=registry.redhat.io/codeready-workspaces/plugin-java11-rhel8@sha256:e86be19ea5c4868f68188a46cec3f4131c1a18400f6800b27d5da92c95c2418b;codeready_workspaces_plugin_java8=registry.redhat.io/codeready-workspaces/plugin-java8-rhel8@sha256:bb8ec9c4964e39b335be589f027c4b5ec866fe5f742c7181473e70fff717655d;codeready_workspaces_plugin_kubernetes=registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8@sha256:f40c6cf67df5294f5d767312633a5ce5cf8b542f660f52f3252c61d6c5342f9e;codeready_workspaces_plugin_openshift=registry.redhat.io/codeready-workspaces/plugin-openshift-rhel8@sha256:a8f9e97a6946bbd5e0ac515621408cb361531bc33c99983f17aaf547a44776a2;codeready_workspaces_stacks_cpp=registry.redhat.io/codeready-workspaces/stacks-cpp-rhel8@sha256:8855029f8658060e79513bd51bad33e38134adf0586286ef2a02bdf27e9dd526;codeready_workspaces_stacks_dotnet=registry.redhat.io/codeready-workspaces/stacks-dotnet-rhel8@sha256:0422cfa23c5eefdda978bbec4f1fc2c24fccfa5a9568d5bda69e3232efefec54;codeready_workspaces_stacks_golang=registry.redhat.io/codeready-workspaces/stacks-golang-rhel8@sha256:de9daf2d87903ebabf03f64e4c15d6f4f7106525396f31bad555ce858864219c;codeready_workspaces_stacks_php=registry.redhat.io/codeready-workspaces/stacks-php-rhel8@sha256:59c41da505474c48617cec3759064db55bab69bf8cd6f9752bfa95b8756dc710;codeready_workspaces_theia=registry.redhat.io/codeready-workspaces/theia-rhel8@sha256:925be51cad7d93eae735039cd76569ef14bdf546876584479a5b037758defc7b;codeready_workspaces_theia_endpoint=registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:42cd00002085280c39534ad856df6adac925218be07ee652b78d92c24cf71573;jboss_eap_7_eap73_openjdk8_openshift_rhel7=registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7@sha256:d16cfe30eaf20a157cd5d5980a6c34f3fcbcfd2fd225e670a0138d81007dd919;jboss_eap_7_eap_xp2_openjdk11_openshift=registry.redhat.io/jboss-eap-7/eap-xp2-openjdk11-openshift-rhel8@sha256:647d092383a760edc083eafb2d7bc3208d6409097281bedbd5eaccde360e7e39;pvc_jobs=registry.redhat.io/ubi8/ubi-minimal@sha256:2f6b88c037c0503da7704bccd3fc73cb76324101af39ad28f16460e7bce98324;rhscl_mongodb_36_rhel7=registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73;'

Note

To use the supported Image Puller, install it separately from the KubernetesImagePuller Operator. Red Hat official build benefits from extra testing and validation provided by Red Hat.

Enabling the use of KubernetesImagePuller in Operator Hub during CodeReady Workspaces installation, sets the Community supported version for use.

Verification steps

OpenShift creates a kubernetes-image-puller-operator Subscription.
The eclipse-che namespace contains a community supported Kubernetes Image Puller Operator ClusterServiceVersion:
```
$ oc get clusterserviceversions
```
The eclipse-che namespace contains these deployments: kubernetes-image-puller and kubernetes-image-puller-operator.
```
$ oc get deployments
```
The community supported Kubernetes Image Puller Operator creates a KubernetesImagePuller Custom Resource:
```
$ oc get kubernetesimagepullers
```

8.4. Installing Image Puller on OpenShift 4 using OperatorHub

This procedure describes how to install the community supported Kubernetes Image Puller Operator on OpenShift 4 using the Operator.

Prerequisites

An administrator account on a running instance of OpenShift 4.
Section 8.1, “Defining the list of images to pull”
Section 8.2, “Defining the memory parameters for the Image Puller”.

Procedure

To create an OpenShift project <kubernetes-image-puller> to host the Image Puller, open the OpenShift web console, navigate to the Home → Projects section and click Create Project.
Specify the project details:
- Name: <kubernetes-image-puller>
- Display Name: <Image Puller>
- Description: <Kubernetes Image Puller>
Navigate to Operators → OperatorHub.
Use the Filter by keyword box to search for community supported Kubernetes Image Puller Operator. Click the community supported Kubernetes Image Puller Operator.
Read the description of the Operator. Click Continue → Install.
Select A specific project on the cluster for the Installation Mode. In the drop-down find the OpenShift project <kubernetes-image-puller>. Click Subscribe.
Wait for the community supported Kubernetes Image Puller Operator to install. Click the KubernetesImagePuller → Create instance.
In a redirected window with a YAML editor, make modifications to the KubernetesImagePuller Custom Resource and click Create.
Navigate to the Workloads and Pods menu in the <kubernetes-image-puller> OpenShift project. Verify that the Image Puller is available.

8.5. Installing Image Puller on OpenShift using OpenShift templates

This procedure describes how to install the Kubernetes Image Puller on OpenShift using OpenShift templates.

Prerequisites

A running OpenShift cluster.
The oc tool is available.
Section 8.1, “Defining the list of images to pull”.
Section 8.2, “Defining the memory parameters for the Image Puller”.

Procedure

Clone the Image Puller repository and get in the directory containing the OpenShift templates:

$ git clone https://github.com/che-incubator/kubernetes-image-puller
$ cd kubernetes-image-puller/deploy/openshift

Configure the app.yaml, configmap.yaml and serviceaccount.yaml OpenShift templates using following parameters:

Table 8.2. Image Puller OpenShift templates parameters in app.yaml

Value	Usage	Default
`DEPLOYMENT_NAME`	The value of `DEPLOYMENT_NAME` in the ConfigMap	`kubernetes-image-puller`
`IMAGE`	Image used for the `kubernetes-image-puller` deployment	`registry.redhat.io/codeready-workspaces/imagepuller-rhel8:2.9`
`IMAGE_TAG`	The image tag to pull	`latest`
`SERVICEACCOUNT_NAME`	The name of the ServiceAccount created and used by the deployment	`kubernetes-image-puller`

Table 8.3. Image Puller OpenShift templates parameters in configmap.yaml

Value	Usage	Default
`CACHING_CPU_LIMIT`	The value of `CACHING_CPU_LIMIT` in the ConfigMap	`.2`
`CACHING_CPU_REQUEST`	The value of `CACHING_CPU_REQUEST` in the ConfigMap	`.05`
`CACHING_INTERVAL_HOURS`	The value of `CACHING_INTERVAL_HOURS` in the ConfigMap	`"1"`
`CACHING_MEMORY_LIMIT`	The value of `CACHING_MEMORY_LIMIT` in the ConfigMap	"20Mi"`
`CACHING_MEMORY_REQUEST`	The value of `CACHING_MEMORY_REQUEST` in the ConfigMap	`"10Mi"`
`DAEMONSET_NAME`	The value of `DAEMONSET_NAME` in the ConfigMap	`kubernetes-image-puller`
`DEPLOYMENT_NAME`	The value of `DEPLOYMENT_NAME` in the ConfigMap	`kubernetes-image-puller`
`IMAGES`	The value of `IMAGES` in the ConfigMap	'che_workspace_plugin_broker_artifacts=registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:c0a096ed1829b21b0641d98c591139324affc0c866a5e011ae6627dd22d316c6;che_workspace_plugin_broker_metadata=registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cd977a7e55dff0d478be81762db17dad3e9daf2cc8f80d168f6e3adcccca3986;codeready_workspaces_machineexec=registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:7bc2f046c1fcb00ab7656de7a7c31da73e71af3164314f77960061102f44c9da;codeready_workspaces_plugin_java11=registry.redhat.io/codeready-workspaces/plugin-java11-rhel8@sha256:e86be19ea5c4868f68188a46cec3f4131c1a18400f6800b27d5da92c95c2418b;codeready_workspaces_plugin_java8=registry.redhat.io/codeready-workspaces/plugin-java8-rhel8@sha256:bb8ec9c4964e39b335be589f027c4b5ec866fe5f742c7181473e70fff717655d;codeready_workspaces_plugin_kubernetes=registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8@sha256:f40c6cf67df5294f5d767312633a5ce5cf8b542f660f52f3252c61d6c5342f9e;codeready_workspaces_plugin_openshift=registry.redhat.io/codeready-workspaces/plugin-openshift-rhel8@sha256:a8f9e97a6946bbd5e0ac515621408cb361531bc33c99983f17aaf547a44776a2;codeready_workspaces_stacks_cpp=registry.redhat.io/codeready-workspaces/stacks-cpp-rhel8@sha256:8855029f8658060e79513bd51bad33e38134adf0586286ef2a02bdf27e9dd526;codeready_workspaces_stacks_dotnet=registry.redhat.io/codeready-workspaces/stacks-dotnet-rhel8@sha256:0422cfa23c5eefdda978bbec4f1fc2c24fccfa5a9568d5bda69e3232efefec54;codeready_workspaces_stacks_golang=registry.redhat.io/codeready-workspaces/stacks-golang-rhel8@sha256:de9daf2d87903ebabf03f64e4c15d6f4f7106525396f31bad555ce858864219c;codeready_workspaces_stacks_php=registry.redhat.io/codeready-workspaces/stacks-php-rhel8@sha256:59c41da505474c48617cec3759064db55bab69bf8cd6f9752bfa95b8756dc710;codeready_workspaces_theia=registry.redhat.io/codeready-workspaces/theia-rhel8@sha256:925be51cad7d93eae735039cd76569ef14bdf546876584479a5b037758defc7b;codeready_workspaces_theia_endpoint=registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:42cd00002085280c39534ad856df6adac925218be07ee652b78d92c24cf71573;jboss_eap_7_eap73_openjdk8_openshift_rhel7=registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7@sha256:d16cfe30eaf20a157cd5d5980a6c34f3fcbcfd2fd225e670a0138d81007dd919;jboss_eap_7_eap_xp2_openjdk11_openshift=registry.redhat.io/jboss-eap-7/eap-xp2-openjdk11-openshift-rhel8@sha256:647d092383a760edc083eafb2d7bc3208d6409097281bedbd5eaccde360e7e39;pvc_jobs=registry.redhat.io/ubi8/ubi-minimal@sha256:2f6b88c037c0503da7704bccd3fc73cb76324101af39ad28f16460e7bce98324;rhscl_mongodb_36_rhel7=registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73;'
`NODE_SELECTOR`	The value of `NODE_SELECTOR` in the ConfigMap	`"{}"`

Table 8.4. Image Puller OpenShift templates parameters in serviceaccount.yaml

Value	Usage	Default
`SERVICEACCOUNT_NAME`	The name of the ServiceAccount created and used by the deployment	`kubernetes-image-puller`

Create an OpenShift project to host the Image Puller:
```
$ oc new-project <kubernetes-image-puller>
```

Process and apply the templates to install the puller:

$ oc process -f serviceaccount.yaml | oc apply -f -
$ oc process -f configmap.yaml | oc apply -f -
$ oc process -f app.yaml | oc apply -f -

Verification steps

Verify the existence of a <kubernetes-image-puller> deployment and a <kubernetes-image-puller> DaemonSet. The DaemonSet needs to have a Pod for each node in the cluster:
```
$ oc get deployment,daemonset,pod --namespace <kubernetes-image-puller>
```

Verify the values of the <kubernetes-image-puller> ConfigMap.

$ oc get configmap <kubernetes-image-puller> --output yaml

Select Your Language

Chapter 8. Caching images for faster workspace start

8.1. Defining the list of images to pull

8.2. Defining the memory parameters for the Image Puller

8.3. Installing Image Puller using the CodeReady Workspaces Operator

8.4. Installing Image Puller on OpenShift 4 using OperatorHub

8.5. Installing Image Puller on OpenShift using OpenShift templates

Quick Links

Help

Site Info

Related Sites

About

Red Hat legal and privacy links

Red Hat legal and privacy links

Language and Page Formatting Options

Chapter 8. Caching images for faster workspace start

8.1. Defining the list of images to pull

8.2. Defining the memory parameters for the Image Puller

8.3. Installing Image Puller using the CodeReady Workspaces Operator

8.4. Installing Image Puller on OpenShift 4 using OperatorHub

8.5. Installing Image Puller on OpenShift using OpenShift templates

Quick Links

Help

Site Info

Related Sites

Systems Status

About

Red Hat legal and privacy links

Red Hat legal and privacy links