The following pages and posts are tagged with

TitleExcerpt
Managing workspaces Creating workspaces Use the stacks in the Dashboard to create a workspace. Images and configuration in these stacks are certified both for Docker and OpenShift. These stacks are used in daily functional testing. Creating a workspace from stacks...
Environment variables Environment variables are defined per machine. Depending on the infrastructure, they are added either to the container or the Kubernetes pod definition. You can add, edit, and remove environment variables either in the User Dashboard or directly in the workspace machine configuration. The following is...
Workspace Environments
Installers What are installers? Installers are scripts that are added into machines in a runtime. Once running, installers: Prepare the environment and download dependencies for a particular software or tool. Install chosen software and dependencies....
Che on Kubernetes: Admin Guide hen the deployment YAML files run, RAM prerequisites Single-user prerequisites 3 GB of RAM is required for single-user Che on Kubernetes. Single-user Che uses RAM in this distribution: Che...
Configuring Kubernetes You can configure the behavior of the Che server by passing environment variables to the Che deployment. There are multiple ways to edit the Che deployment to add new or edit existing environment variables: To open the Che deployment YAML...
Deploying multi-user Che to Kubernetes This section walks you through multi-user deployment of Che on Kubernetes. Prerequisites A Kubernetes cluster with at least 4 GB RAM and RBAC: For Minikube 0.26.0 and higher, use the following command: ...
Deploying single-user Che to Kubernetes This section walks you through single-user deployment of Che on Kubernetes. Prerequisites A Kubernetes cluster with at least 4 GB RAM and RBAC: For Minikube 0.26.0 and higher, use the following command: ...
Che on OpenShift: Admin Guide :page-layout: _auto :admin-context: OpenShift :ctl-command: oc :k8s-namespace: OpenShift Project :docs-registry-link: https://docs.okd.io/latest/architecture/infrastructure_components/image_registry.html :che-data-volume-link: https://github.com/eclipse/che/blob/master/deploy/openshift/templates/pvc/che-server-pvc.yaml#L14 :cluster-nodes-link: https://docs.okd.io/latest/admin_guide/manage_nodes.html include::../setup-kubernetes/kubernetes-or-openshift-admin-guide.adoc[] [id="create-workspace-objects-in-personal-namespaces"] == Creating workspace objects in personal namespaces You can register the OpenShift server as an identity provider when Che is installed in multi-user mode. This allows you to create workspace objects in the...
Projects :page-layout: _auto [id="creating-projects-in-workspaces"] == Creating projects in workspaces Projects are always associated with a workspace and saved in a workspace configuration. The following is an example of the project YAML file: [source,json] ---- "projects": [ { "description": "A basic example using Spring servlets. The app returns values entered into a...
Recipes :page-layout: _auto [id="supported-recipe-formats"] == Supported Recipe Formats Depending on the infrastructure, Che supports the following default recipe formats: [cols=",,,,",options="header",] |=== |*Infrastructure* |*Docker-formatted container image* |*Dockerfile* |*Composefile* |*Kubernetes YAML* |*Docker* |Supported |Supported |Supported |Not supported |*OpenShift* |Supported |Not supported |Not supported |Supported |=== [id="docker-formatted-container-image-requirements-and-limitations"] == Docker-formatted container image requirements and limitations...
Secure Servers :page-layout: _auto Now that you have made yourself familiar with link:servers.html#secure-server[secure servers] concept, let’s take a closer look at enabling this functionality and implementation details. [id="how-to-enable-secure-servers-functionality"] == How to enable secure servers functionality? This functionality is in *beta* phase now and it is disabled by default. It is needed to...
Servers :page-layout: _auto [id="what-are-servers"] == What are servers? A server defines the protocol port of a process that runs in a machine. It has a name, path, and attributes. The path defines the base path of the service that is used by the server. Attributes are optional and can be used...
Stacks :page-layout: _auto [id="stack-overview"] == Stack overview A stack is a link:workspace-data-model.html[workspace configuration] template. Stacks are used to create workspaces in the *User Dashboard*. The stack includes meta-information such as scope, tags, components, description, name, and identification. You can filter stacks by machine type and scope. The type is either single...
Volumes :page-layout: _auto [id="default-volumes_for_workspace_containers"] == Default volumes for workspace containers By default, workspace containers start with a default volume and have a minimum of one PVC that is located in the `/projects` directory. Workspace projects are physically located in the `/projects` directory. When a workspace stops, the machines are destroyed, but...
Administering workspaces :page-layout: _auto IMPORTANT: Che 6 workspace configuration format is no longer supported in the latest Che 7 release. Please, follow the link:{site-baseurl}che-7/converting-a-che-6-workspace-to-a-che-7-devfile["Converting a Che 6 workspace to a Che 7 devfile"] documentation in order to update the definition of the workspace and benefit from the latest capabilities. [id="workspace"] == Workspace...
Workspace Data Model :page-layout: _auto The following table lists the data types and their description. [width="100%",cols="50%,50%",options="header",] |=== |Data Types |Description |environments: Map |Workspace environment variables. A workspace can have multiple environment variables. |defaultEnv: STRING |A workspace must have a default environment. |projects: [] |Projects associated with a workspace. |commands: [] |Commands associated...
Workspace REST API :page-layout: _auto
Troubleshooting failures in starting the workspace :page-layout: _auto Failures to start a workspace may be caused by the following factors: * Incorrect environment recipe * Restrictive network settings [id="bad-recipes"] == Incorrect environment recipes When a workspace is starting, an environment link:recipes.html[recipe] is sent to Docker or to the OpenShift API. The Che server then listens to...