See the Installing CodeReady Workspaces chapter of the Administration Guide.

For Red Hat CodeReady Workspaces 1.0.2, Red Hat will provide support for deployment, configuration, and use of the product. CodeReady Workspaces.

CodeReady Workspaces 1.0.2 has been tested on Chrome version 71.0.3578.98 (Official Build) (64-bit).

For more information, see CodeReady Workspaces life-cycle and support policy.

CodeReady Workspaces provides a centralized platform on OpenShift to define, administer, and manage developer environments. It simplifies the configuration of developer tools and secures access to the source code.

The product provides developer workspaces running on OpenShift. The workspaces run as pods and support multi-container configurations for developing microservices-based applications. Production environments can be replicated into the developer workspaces.

CodeReady Workspaces bundles a rich, browser-based IDE with language tooling, autocompletion, refactoring, code navigation, debuggers, terminal to access containers, Git integration, and more.

Pre-built stacks with supported Red Hat technologies can be used, or custom stacks can be created and shared across the developer teams.

The following stacks are supported by Red Hat for use with CodeReady Workspaces 1.0.2:

The following stacks are supported by Red Hat as Beta for use with CodeReady Workspaces 1.0.2:

The following stacks are supported by Red Hat as Technology Preview for use with CodeReady Workspaces 1.0.2:

So-called factories allow to share developer workspaces. A factory URL can be used in any development workflow to simplify developer onboarding.

Includes Red Hat SSO to handle authentication and security between the developer teams. Allows integration with LDAP or AD.

Create teams, reflect the structure of your organization, and share pre-configured workspace stacks.

With factories, it is easy to generate and integrate developer workspaces that will be available on-demand from any tools used by the team (and the stakeholders).

Connect to the developer workspaces from Eclipse or other tools using SSH.

CodeReady Workspaces features limited secured entry points and identity checks for each developer. Fine-grained permissions can be used to share resources.

Insights about application dependencies: security vulnerabilities, license compatibility, and AI-based guidance for additional, alternative dependencies.

The Analytics plug-in is enabled by default in the Java and NodeJS stacks in CodeReady Workspaces. The plug-in analyzes all project dependencies and shows a report with warnings for CVEs or issues with any of the dependencies. A language server provides in-context analysis of the dependencies. When editing a pom.xml or package.json file, the server doisplays errors, warnings, and recommendations.

A second deployment of CodeReady Workspaces to the same OpenShift Container Platform cluster causes the oAuth secret in the openshift-oauth-client client to be rewritten. It is recommended not to deploy multiple instances of CodeReady Workspaces top the same OpenShift Container Platform cluster.

To work around this issue, manually create another oAuth client with the right redirecURI, secret, and name.

The deployment script does not have an option to continue a deployment that was interrupted or previously failed. When the installation is interrupted before it successfully completes, the used namespace needs to be manually cleared of incomplete deployment artefacts.

Following an interrupted or failed deployment, select the used namespace and deployments, pods, and secrets, as well as the Che configuration map. Then repeat the deployment process from the start.

Provided the two following conditions are met, it will not be possible to run two or more workspaces at the same time:

To work around this limitation, use one of the two following measures:

When the per-workspace PVC (Persistent Volume Claim) strategy is configured, workspaces fail to start correctly. Workspace start is extremely slow because the pod that is launched to create directories in the PVC is attempting to mount a wrong PVC.

To work around this issue, set the CHE_INFRA_KUBERNETES_PVC_PRECREATE__SUBPATHS environment variable to false in the che configuration map, and restart CodeReady Workspaces.

When the per-workspace PVC (Persistent Volume Claim) strategy is configured, associated PVC (Persistent Volume Claim) is not removed nor cleaned up when deleting a workspace. To avoid encountering this issue, do not use the per-workspace PVC strategy (instead, use the common or unique strategy).

Alternatively, the associated PVC can be deleted manually using the oc delete pvc <pvc_name_or_id> command.

When proxy settings are configured in the config.yaml configuration file, the deployment fails. No workaround is available for this issue.

When CodeReady Workspaces is installed with TLS and OpenShift oAuth support, authentication on the CodeReady Workspaces login page fails with the following error message: Unexpected error when authenticating with identity provider.