Chapter 3. Installing CodeReady Workspaces

This section contains instructions to install Red Hat CodeReady Workspaces. The installation method depends on the target platform and the environment restrictions.

3.1. Installing CodeReady Workspaces on OpenShift 4 using OperatorHub

This section describes how to install CodeReady Workspaces using the CodeReady Workspaces Operator available in OpenShift 4 web console.

Operators are a method of packaging, deploying, and managing an OpenShift application which also provide the following:

Repeatability of installation and upgrade.
Constant health checks of every system component.
Over-the-air (OTA) updates for OpenShift components and independent software vendor (ISV) content.
A place to encapsulate knowledge from field engineers and spread it to all users.

Prerequisites

An administrator account on a running instance of OpenShift 4.

3.1.1. Creating a project in OpenShift Web Console

A project allows to organize and manage different resources on the cluster in an isolated unit. Create a project first to host the Red Hat CodeReady Workspaces Operator.

Procedure

Open the OpenShift web console, in the left panel navigate to the Home → Projects section.
Click Create Project.
Specify the project details:
- Name: openshift-workspaces
- Display Name: Red Hat CodeReady Workspaces
- Description: Red Hat CodeReady Workspaces

3.1.2. Installing the Red Hat CodeReady Workspaces Operator

Red Hat CodeReady Workspaces Operator provides all the resources for running CodeReady Workspaces, such as PostgreSQL, RH-SSO, image registries, and the CodeReady Workspaces server, and also configures all these services.

Prerequisites

Access to the Web Console on the cluster.

Procedure

To install the Red Hat CodeReady Workspaces Operator, in the left panel, navigate to the Operators → OperatorHub section.
In the Filter by keyword field, type Red Hat CodeReady Workspaces and click the Red Hat CodeReady Workspaces tile.
In the Red Hat CodeReady Workspaces pop-up window, click the Install button.
On the Install Operator screen, specify the following options:
- Installation mode: A specific project on the cluster
- Installed Namespace: *Pick an existing project → openshift-workspaces

Verification steps

To verify the Red Hat CodeReady Workspaces Operator has installed correctly, in the left panel navigate to the Operators → Installed Operators section.
In the Installed Operators screen, click the Red Hat CodeReady Workspaces name and navigate to the Details tab.
In the ClusterServiceVersion Details section at the bottom of the page, wait for these messages:
- Status: Succeeded
- Status Reason: install strategy completed with no errors
Navigate to the Events tab and wait for this message: install strategy completed with no errors.

3.1.3. Creating an instance of the Red Hat CodeReady Workspaces Operator

Follow this procedure to install Red Hat CodeReady Workspaces with the default configuration. To modify the configuration, see Chapter 2, Configuring the CodeReady Workspaces installation.

Procedure

To create an instance of the Red Hat CodeReady Workspaces Operator, in the left panel, navigate to the Operators → Installed Operators section.
In the Installed Operators screen, click the Red Hat CodeReady Workspaces name.
In the Operator Details screen, in the Details tab, inside of the Provided APIs section, click the Create Instance link.
The Create CheCluster page contains the configuration of the overall CodeReady Workspaces instance to create. It is the CheCluster Custom Resource. Keep the default values.
To create the codeready-workspaces cluster, click the Create button in the lower left corner of the window.
On the Operator Details screen, in the Red Hat CodeReady Workspaces Cluster tab, click on the codeready-workspaces link.
To navigate to the codeready-workspaces instance, click the link under Red Hat CodeReady Workspaces URL.
Note
The installation might take more than 5 minutes. The URL appears after the Red Hat CodeReady Workspaces installation finishes.

Verification steps

To verify that the Red Hat CodeReady Workspaces instance has installed correctly, navigate to the CodeReady Workspaces Cluster tab. The CheClusters screen displays the list of Red Hat CodeReady Workspaces instances and their status.
Click codeready-workspaces CheCluster in the table and navigate to the Details tab.
See the content of following fields:
- Message: the field contains error messages, if any. The expected content is None.
- Red Hat CodeReady Workspaces URL: displays the URL of the Red Hat CodeReady Workspaces instance, once the deployment is successful.
Navigate to the Resources tab. The screen displays the list of the resources assigned to the CodeReady Workspaces deployment.
To see more details about the state of a resource, click its name and inspect the content of the available tabs.

Additional resources

https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.4/html-single/end-user_guide/index#navigating-codeready-workspaces-using-the-dashboard_crw.
https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.4/html-single/administration_guide/index#viewing-operator-events.adoc.
It is possible to use the crwctl utility script for deploying CodeReady Workspaces on OpenShift Container Platform and OpenShift Dedicated versions 4.5. This method is unofficial and serves as a backup installation method for situations where the installation method using OperatorHub is not available. See the Section 3.2.2, “Installing CodeReady Workspaces on OpenShift 3 using the Operator” section.

3.2. Installing CodeReady Workspaces on OpenShift Container Platform 3.11

3.2.1. Installing the crwctl CLI management tool

This section describes how to install crwctl, the CodeReady Workspaces CLI management tool.

Procedure

Navigate to https://developers.redhat.com/products/codeready-workspaces/download.
Download the CodeReady Workspaces CLI management tool archive for version 2.4.
Extract the archive to a folder, such as ${HOME}/crwctl or /opt/crwctl.
Run the crwctl executable from the extracted folder. In this example, ${HOME}/crwctl/bin/crwctl version.
Optionally, add the bin folder to your $PATH, for example, PATH=${PATH}:${HOME}/crwctl/bin to enable running crwctl without the full path specification.

Verification step

Running crwctl version displays the current version of the tool.

3.2.2. Installing CodeReady Workspaces on OpenShift 3 using the Operator

This section describes how to install CodeReady Workspaces on OpenShift 3 with the crwctl CLI management tool. The method of installation is using the Operator and enable TLS (HTTPS).

Note

Methods for updating from a previous CodeReady Workspaces installation and enabling multiple instances in the same OpenShift Container Platform 3.11 cluster are provided below the installation procedure.

Operators are a method of packaging, deploying, and managing a OpenShift application which also provide the following:

Repeatability of installation and upgrade.
Constant health checks of every system component.
Over-the-air (OTA) updates for OpenShift components and independent software vendor (ISV) content.
A place to encapsulate knowledge from field engineers and spread it to all users.

Tip

This approach is only supported for use with OpenShift Container Platform and OpenShift Dedicated version 3.11, but also work for newer versions of OpenShift Container Platform and OpenShift Dedicated, and serves as a backup installation method for situations when the installation method using OperatorHub is not available.

Prerequisites

Administrator rights on a running instance of OpenShift 3.11.
An installation of the oc OpenShift 3.11 CLI management tool. See Installing the OpenShift 3.11 CLI.
An installation of the crwctl management tool. See Section 3.2.1, “Installing the crwctl CLI management tool”.
To apply settings that the main crwctl command-line parameters cannot set, prepare a configuration file operator-cr-patch.yaml that will override the default values in the CheCluster Custom Resource used by the Operator. See Chapter 2, Configuring the CodeReady Workspaces installation.
<namespace> represents the project of the target installation.

Procedure

Log in to OpenShift. See Basic Setup and Login.
```
$ oc login
```
Run the following command to verify that the version of the oc OpenShift CLI management tool is 3.11:
```
$ oc version
oc v3.11.0+0cbc58b
```
Run the following command to create the CodeReady Workspaces instance
- In the user-defined <namespace>:
```
$ crwctl server:start -n <namespace> -p openshift
```
- In the default project called openshift-workspaces:
```
$ crwctl server:start -p openshift
```

Verification steps

The output of the previous command ends with:

Command server:start has completed successfully.

Navigate to the CodeReady Workspaces cluster instance: https://codeready-<openshift_deployment_name>.<domain_name>.

Upgrading from a previous CodeReady Workspaces installation

To upgrade from a previous CodeReady Workspaces installation in the same OpenShift Container Platform 3.11 cluster, remove the Custom Resource Definition and the Cluster Roles:

$ oc delete customresourcedefinition/checlusters.org.eclipse.che
$ oc patch customresourcedefinition/checlusters.org.eclipse.che \
    --type merge \
    -p '{ "metadata": { "finalizers": null }}'
$ oc delete clusterrole codeready-operator

Having multiple CodeReady Workspaces deployments

To have multiple CodeReady Workspaces deployments in parallel using different versions in the same OpenShift Container Platform 3.11 cluster, create a new service account for the new deployment. It is, however, strongly recommended that you update all your old CodeReady Workspaces deployments to the latest version instead, as this mix of versions may cause unexpected and unsupported results.
```
$ oc patch clusterrolebinding codeready-operator \
    --type='json' \
    -p '[{"op": "add", "path": "/subjects/0", "value": {"kind":"ServiceAccount", "namespace": "<openshift-workspaces>", "name": "codeready-operator"} }]'
```

3.3. Installing CodeReady Workspaces in a restricted enviroment

By default, Red Hat CodeReady Workspaces uses various external resources, mainly container images available in public registries.

To deploy CodeReady Workspaces in an environment where these external resources are not available (for example, on a cluster that is not exposed to the public Internet):

Identify the image registry used by the OpenShift cluster, and ensure you can push to it.
Push all the images needed for running CodeReady Workspaces to this registry.
Configure CodeReady Workspaces to use the images that have been pushed to the registry.
Proceed to the CodeReady Workspaces installation.

The procedure for installing CodeReady Workspaces in restricted environments is different based on the installation method you use:

Notes on network connectivity in restricted environments

Restricted network environments range from a private subnet in a cloud provider to a separate network owned by a company, disconnected from the public Internet. Regardless of the network configuration, CodeReady Workspaces works provided that the Routes that are created for CodeReady Workspaces components (codeready-workspaces-server, identity provider, devfile and plugin registries) are accessible from inside the OpenShift cluster.

Take into account the network topology of the environment to determine how best to accomplish this. For example, on a network owned by a company or an organization, the network administrators must ensure that traffic bound from the cluster can be routed to Route hostnames. In other cases, for example, on AWS, create a proxy configuration allowing the traffic to leave the node to reach an external-facing Load Balancer.

When the restricted network involves a proxy, follow the instructions provided in Section 3.3.3, “Preparing CodeReady Workspaces Custom Resource for installing behind a proxy”.

3.3.1. Installing CodeReady Workspaces in a restricted environment using OperatorHub

Prerequisites

A running OpenShift cluster. See the OpenShift Container Platform 4.3 documentation for instructions on how to install an OpenShift cluster on a restricted network.
Access to the mirror registry used to installed the OpenShift disconnected cluster in restricted network. See the Related OpenShift Container Platform 4.3 documentation about creating a mirror registry for installation in a restricted network.

On disconnected OpenShift 4 clusters running on restricted networks, an Operator can be successfully installed from OperatorHub only if it meets the additional requirements defined in Enabling your Operator for restricted network environments.

The CodeReady Workspaces operator meets these requirements and is therefore compatible with the official documentation about OLM on a restricted network.

Procedure

To install CodeReady Workspaces from OperatorHub:

Build a redhat-operators catalog image. See Building an Operator catalog image.
Configure OperatorHub to use this catalog image for operator installations. See Configuring OperatorHub for restricted networks.
Proceed to the CodeReady Workspaces installation as usual as described in Section 3.1, “Installing CodeReady Workspaces on OpenShift 4 using OperatorHub”.

3.3.2. Installing CodeReady Workspaces in a restricted environment using CLI management tool

Note

Use CodeReady Workspaces CLI management tool to install CodeReady Workspaces on restricted networks if installation through OperatorHub is not available. This method is supported for OpenShift Container Platform 3.11.

Prerequisites

A running OpenShift cluster. See the OpenShift Container Platform 3.11 documentation for instructions on how to install an OpenShift cluster.

3.3.2.1. Preparing a private registry

Prerequisites

The oc tool is available.
The skopeo tool, version 0.1.40 or later, is available.
The podman tool is available.
An image registry accessible from the OpenShift cluster and supporting the format of the V2 image manifest, schema version 2. Ensure you can push to it from a location having, at least temporarily, access to the internet.

Table 3.1. Placeholders used in examples

`<source-image>`	Full coordinates of the source image, including registry, organization, and digest.
`<target-registry>`	Host name and port of the target container-image registry.
`<target-organization>`	Organization in the target container-image registry
`<target-image>`	Image name and digest in the target container-image registry.
`<target-user>`	User name in the target container-image registry.
`<target-password>`	User password in the target container-image registry.

Procedure

Log into the internal image registry:
```
$ podman login --username <user> --password <password> <target-registry>
```
Tip
If you meet an error, such as x509: certificate signed by unknown authority, when attempting to push to the internal registry, try one of these workarounds:
- add the OpenShift cluster’s certificate to /etc/containers/certs.d/<target-registry>
- add the registry as an insecure registry by adding the following lines to the Podman configuration file located at /etc/containers/registries.conf:
```
[registries.insecure]
registries = ['<target-registry>']
```

Copy images without changing their digest. Repeat this step for every image in the following table:

$ skopeo copy --all docker://<source-image> \
  docker://<target-registry>/<target-organization>/<target-image>

Note

Table 3.2. Understanding the usage of the container-images from the prefix or keyword they include in their name

Usage	Prefix or keyword
Essential	not `stacks-`, `plugin-`, or `-openj-`
Workspaces	`stacks-`, `plugin-`
Z and Power	`-openj-`

Table 3.3. Images to copy in the private registry

Verify the images have the same digests:

$ skopeo inspect docker://<source-image>
$ skopeo inspect docker://<target-registry>/<target-organization>/<target-image>

Set the digests explicitly when different:

$ skopeo copy --all docker://<source-image> \
  docker://<target-registry>/<target-organization>/<target-image>

Additional resources

To find the sources of the images list, see the values of the relatedImages attribute in the CodeReady Workspaces Operator ClusterServiceVersion sources.

3.3.2.2. Preparing CodeReady Workspaces Custom Resource for restricted environment

When installing CodeReady Workspaces in a restricted environment using crwctl or OperatorHub, provide a CheCluster custom resource with additional information.

3.3.2.2.1. Downloading the default `CheCluster` Custom Resource

Procedure

Download the default custom resource YAML file.
Name the downloaded custom resource org_v1_che_cr.yaml. Keep it for further modification and usage.

3.3.2.2.2. Customizing the `CheCluster` Custom Resource for restricted environment

Prerequisites

All required images available in an image registry that is visible to the OpenShift cluster where CodeReady Workspaces is to be deployed. This is described in Section 3.3.2.1, “Preparing a private registry”, where the placeholders used in the following examples are also defined.

Procedure

In the CheCluster Custom Resource, which is managed by the CodeReady Workspaces Operator, add the fields used to facilitate deploying an instance of CodeReady Workspaces in a restricted environment:
```
# [...]
spec:
  server:
    airGapContainerRegistryHostname: '<image-registry>'
    airGapContainerRegistryOrganization: '<organization>'
# [...]
```

3.3.2.3. Starting CodeReady Workspaces installation in a restricted environment using CodeReady Workspaces CLI management tool

This sections describes how to start the CodeReady Workspaces installation in a restricted environment using the CodeReady Workspaces CLI management tool.

Prerequisites

CodeReady Workspaces CLI management tool is installed. See Section 3.2.1, “Installing the crwctl CLI management tool”.
The oc tool is installed.
Access to an OpenShift instance.

Procedure

$ oc login ${OPENSHIFT_API_URL} --username ${OPENSHIFT_USERNAME} \
                                --password ${OPENSHIFT_PASSWORD}

Install CodeReady Workspaces with a customized Custom Resource to add fields related to the restricted environment:

$ crwctl server:start \
  --che-operator-image=<image-registry>/<organization>/crw-2-rhel8-operator:2.4 \
  --che-operator-cr-yaml=org_v1_che_cr.yaml

Note

For slow systems or internet connections, add the --k8spodwaittimeout=1800000 option to the crwctl server:start command to extend the Pod timeout period to 1800000 ms or longer.

3.3.3. Preparing CodeReady Workspaces Custom Resource for installing behind a proxy

This procedure describes how to provide necessary additional information to the CheCluster custom resource when installing CodeReady Workspaces behind a proxy.

Procedure

In the CheCluster Custom Resource, which is managed by the CodeReady Workspaces Operator, add the fields used to facilitate deploying an instance of CodeReady Workspaces in a restricted environment:
```
# [...]
spec:
  server:
    proxyURL: '<URL of the proxy, with the http protocol, and without the port>'
    proxyPort: '<Port of proxy, typically 3128>'
# [...]
```
In addition to those basic settings, the proxy configuration usually requires adding the host of the external OpenShift cluster API URL in the list of the hosts to be accessed from CodeReady Workspaces without using the proxy.
To retrieve this cluster API host, run the following command against the OpenShift cluster:
```
$ oc whoami --show-server | sed 's#https://##' | sed 's#:.*$##'
```
The corresponding field of the CheCluster Custom Resource is nonProxyHosts. If a host already exists in this field, use | as a delimiter to add the cluster API host:
```
# [...]
spec:
  server:
    nonProxyHosts: 'anotherExistingHost|<cluster api host>'
# [...]
```

Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

Chapter 3. Installing CodeReady Workspaces

3.1. Installing CodeReady Workspaces on OpenShift 4 using OperatorHub

3.1.1. Creating a project in OpenShift Web Console

3.1.2. Installing the Red Hat CodeReady Workspaces Operator

3.1.3. Creating an instance of the Red Hat CodeReady Workspaces Operator

3.2. Installing CodeReady Workspaces on OpenShift Container Platform 3.11

3.2.1. Installing the crwctl CLI management tool

3.2.2. Installing CodeReady Workspaces on OpenShift 3 using the Operator

3.3. Installing CodeReady Workspaces in a restricted enviroment

3.3.1. Installing CodeReady Workspaces in a restricted environment using OperatorHub

3.3.2. Installing CodeReady Workspaces in a restricted environment using CLI management tool

3.3.2.1. Preparing a private registry

3.3.2.2. Preparing CodeReady Workspaces Custom Resource for restricted environment

3.3.2.2.1. Downloading the default `CheCluster` Custom Resource

3.3.2.2.2. Customizing the `CheCluster` Custom Resource for restricted environment

3.3.2.3. Starting CodeReady Workspaces installation in a restricted environment using CodeReady Workspaces CLI management tool

3.3.3. Preparing CodeReady Workspaces Custom Resource for installing behind a proxy

<source-image>	<target-image>
`registry.redhat.io/codeready-workspaces/crw-2-rhel8-operator@sha256:89763ddec38a5925a052fa7ea75fc5a0db39124cada1e2d33b6eba3e32e8a7c6`	`crw-2-rhel8-operator@sha256:89763ddec38a5925a052fa7ea75fc5a0db39124cada1e2d33b6eba3e32e8a7c6`
`registry.redhat.io/codeready-workspaces/devfileregistry-rhel8@sha256:7702adb0ed28b635e45804e87fe5dd98bdd3aa766fed7845a8ce509b91c22e36`	`devfileregistry-rhel8@sha256:7702adb0ed28b635e45804e87fe5dd98bdd3aa766fed7845a8ce509b91c22e36`
`registry.redhat.io/codeready-workspaces/jwtproxy-rhel8@sha256:8afecd5b0edc7734532ee76ff9eac1fc4814d8aaa6c9be440a2a88a20c014e4e`	`jwtproxy-rhel8@sha256:8afecd5b0edc7734532ee76ff9eac1fc4814d8aaa6c9be440a2a88a20c014e4e`
`registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:c9bebc895e5fa5a0bd4ecaedfd5384ab75a45a96b6314ba5d4a6f4c1e8e109f9`	`machineexec-rhel8@sha256:c9bebc895e5fa5a0bd4ecaedfd5384ab75a45a96b6314ba5d4a6f4c1e8e109f9`
`registry.redhat.io/codeready-workspaces/plugin-java11-openj9-rhel8@sha256:27a71612f9bd3bee77adb4e164c44c61cf5085458d592215b2fe74c55d11abc6`	`plugin-java11-openj9-rhel8@sha256:27a71612f9bd3bee77adb4e164c44c61cf5085458d592215b2fe74c55d11abc6`
`registry.redhat.io/codeready-workspaces/plugin-java11-rhel8@sha256:e9deebbc320d28a2f425e858ed3dcf87fc67a40f6654d6eb7c2b6feea022b7d6`	`plugin-java11-rhel8@sha256:e9deebbc320d28a2f425e858ed3dcf87fc67a40f6654d6eb7c2b6feea022b7d6`
`registry.redhat.io/codeready-workspaces/plugin-java8-openj9-rhel8@sha256:14f2774e92b70d85280e506f81e2ea9a89c26490fd53a4421df8a694bd944d2d`	`plugin-java8-openj9-rhel8@sha256:14f2774e92b70d85280e506f81e2ea9a89c26490fd53a4421df8a694bd944d2d`
`registry.redhat.io/codeready-workspaces/plugin-java8-rhel8@sha256:d04f70c8340abaee1a282b77158d054f4faf2225bc17c79aafb413396c367782`	`plugin-java8-rhel8@sha256:d04f70c8340abaee1a282b77158d054f4faf2225bc17c79aafb413396c367782`
`registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8@sha256:d87aed64704369a50d1e54a57815b699f74d4efad1401d1a638808e655a37e48`	`plugin-kubernetes-rhel8@sha256:d87aed64704369a50d1e54a57815b699f74d4efad1401d1a638808e655a37e48`
`registry.redhat.io/codeready-workspaces/plugin-openshift-rhel8@sha256:9c43a02b0dd0f66744359c5ccdb1f1780ecd92c3dc31b14d73b553ba763af8ab`	`plugin-openshift-rhel8@sha256:9c43a02b0dd0f66744359c5ccdb1f1780ecd92c3dc31b14d73b553ba763af8ab`
`registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:d0eebf2c8b460adb75dc6bc5200aa9fd40d030b7b17c6b1c3b9d3c879f4652ee`	`pluginbroker-artifacts-rhel8@sha256:d0eebf2c8b460adb75dc6bc5200aa9fd40d030b7b17c6b1c3b9d3c879f4652ee`
`registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:cff23432d1d397bbbc7df65be9d6ddf4a97a3ef1801708bb7bb7d2fa72dbcce3`	`pluginbroker-metadata-rhel8@sha256:cff23432d1d397bbbc7df65be9d6ddf4a97a3ef1801708bb7bb7d2fa72dbcce3`
`registry.redhat.io/codeready-workspaces/pluginregistry-rhel8@sha256:9f37917122c20fc83e6558a5484efab42650958b513a22920f449f948e50cd51`	`pluginregistry-rhel8@sha256:9f37917122c20fc83e6558a5484efab42650958b513a22920f449f948e50cd51`
`registry.redhat.io/codeready-workspaces/server-rhel8@sha256:63bf304cd04576048012693e7e8544a5a703790f99551554a75798bc799b112b`	`server-rhel8@sha256:63bf304cd04576048012693e7e8544a5a703790f99551554a75798bc799b112b`
`registry.redhat.io/codeready-workspaces/stacks-cpp-rhel8@sha256:56543cfeeeac030821557ac4937db40f6845e874193c79c30267a680f9b2cbe7`	`stacks-cpp-rhel8@sha256:56543cfeeeac030821557ac4937db40f6845e874193c79c30267a680f9b2cbe7`
`registry.redhat.io/codeready-workspaces/stacks-dotnet-rhel8@sha256:13628110b96de0e516ff2dfa29cdcaee64cd8f8978052c8160c294c332dba9f0`	`stacks-dotnet-rhel8@sha256:13628110b96de0e516ff2dfa29cdcaee64cd8f8978052c8160c294c332dba9f0`
`registry.redhat.io/codeready-workspaces/stacks-golang-rhel8@sha256:fef91718ccebc4cd9b89999f6b5df83bf3d60fce657f6f44eda092100549af2c`	`stacks-golang-rhel8@sha256:fef91718ccebc4cd9b89999f6b5df83bf3d60fce657f6f44eda092100549af2c`
`registry.redhat.io/codeready-workspaces/stacks-php-rhel8@sha256:b75f498954fbe858c74f80a89d132ba3560f40c0f697b0cd9550ed5663078ef6`	`stacks-php-rhel8@sha256:b75f498954fbe858c74f80a89d132ba3560f40c0f697b0cd9550ed5663078ef6`
`registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:942e1e6328169508e3fff8fd96c575d7a423339ced17dbf5813d61d1971adaef`	`theia-endpoint-rhel8@sha256:942e1e6328169508e3fff8fd96c575d7a423339ced17dbf5813d61d1971adaef`
`registry.redhat.io/codeready-workspaces/theia-rhel8@sha256:78edc9f75680cbe7f63774d9dfbbc505401486a73c8e420380e1d3078bdf9f2a`	`theia-rhel8@sha256:78edc9f75680cbe7f63774d9dfbbc505401486a73c8e420380e1d3078bdf9f2a`
`registry.redhat.io/jboss-eap-7/eap-xp1-openj9-11-openshift-rhel8@sha256:d6a7bdbf4726fe0e0e54c0bce9b2257bbd2a165c37cb4ec68e1f994716ffb15c`	`eap-xp1-openj9-11-openshift-rhel8@sha256:d6a7bdbf4726fe0e0e54c0bce9b2257bbd2a165c37cb4ec68e1f994716ffb15c`
`registry.redhat.io/jboss-eap-7/eap-xp1-openjdk11-openshift-rhel8@sha256:94e1cd4eb4196a358e301c1992663258c0016c80247f507fd1c39cf9a73da833`	`eap-xp1-openjdk11-openshift-rhel8@sha256:94e1cd4eb4196a358e301c1992663258c0016c80247f507fd1c39cf9a73da833`
`registry.redhat.io/jboss-eap-7/eap73-openjdk8-openshift-rhel7@sha256:24dea0cfc154a23c1aeb6b46ade182d0f981362f36b7e6fb9c7d8531ac639fe0`	`eap73-openjdk8-openshift-rhel7@sha256:24dea0cfc154a23c1aeb6b46ade182d0f981362f36b7e6fb9c7d8531ac639fe0`
`registry.redhat.io/rh-sso-7/sso74-openj9-openshift-rhel8@sha256:8e6c7874247053df431c25552c6e2edb050b2627ae21907149f419e0d9909135`	`sso74-openj9-openshift-rhel8@sha256:8e6c7874247053df431c25552c6e2edb050b2627ae21907149f419e0d9909135`
`registry.redhat.io/rh-sso-7/sso74-openshift-rhel8@sha256:ec6801343eb1ca085154d8d7481552f2e9debc414125413d25e42216aa5922af`	`sso74-openshift-rhel8@sha256:ec6801343eb1ca085154d8d7481552f2e9debc414125413d25e42216aa5922af`
`registry.redhat.io/rhel8/postgresql-96@sha256:fdc2398a25530547354714f2538c691d91b700e0cedef5361a3e7d96ddfd4e11`	`postgresql-96@sha256:fdc2398a25530547354714f2538c691d91b700e0cedef5361a3e7d96ddfd4e11`
`registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73`	`mongodb-36-rhel7@sha256:9f799d356d7d2e442bde9d401b720600fd9059a3d8eefea6f3b2ffa721c0dc73`
`registry.redhat.io/ubi8-minimal@sha256:5cfbaf45ca96806917830c183e9f37df2e913b187aadb32e89fd83fa455ebaa6`	`ubi8-minimal@sha256:5cfbaf45ca96806917830c183e9f37df2e913b187aadb32e89fd83fa455ebaa6`

Chapter 3. Installing CodeReady Workspaces

3.1. Installing CodeReady Workspaces on OpenShift 4 using OperatorHub

3.1.1. Creating a project in OpenShift Web Console

3.1.2. Installing the Red Hat CodeReady Workspaces Operator

3.1.3. Creating an instance of the Red Hat CodeReady Workspaces Operator

3.2. Installing CodeReady Workspaces on OpenShift Container Platform 3.11

3.2.1. Installing the crwctl CLI management tool

3.2.2. Installing CodeReady Workspaces on OpenShift 3 using the Operator

3.3. Installing CodeReady Workspaces in a restricted enviroment

3.3.1. Installing CodeReady Workspaces in a restricted environment using OperatorHub

3.3.2. Installing CodeReady Workspaces in a restricted environment using CLI management tool

3.3.2.1. Preparing a private registry

3.3.2.2. Preparing CodeReady Workspaces Custom Resource for restricted environment

3.3.2.2.1. Downloading the default CheCluster Custom Resource

3.3.2.2.2. Customizing the CheCluster Custom Resource for restricted environment

3.3.2.3. Starting CodeReady Workspaces installation in a restricted environment using CodeReady Workspaces CLI management tool

3.3.3. Preparing CodeReady Workspaces Custom Resource for installing behind a proxy

3.3.2.2.1. Downloading the default `CheCluster` Custom Resource

3.3.2.2.2. Customizing the `CheCluster` Custom Resource for restricted environment