<p>The following pages and posts are tagged with <button type="button" style="cursor: default" class="btn btn-default navbar-btn">kubernetes</button></p> <table><thead><tr><th>Title</th><th>Excerpt</th></tr></thead> <tbody>

<tr><td><a href="creating-starting-workspaces.html">Workspace Management</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Creating Workspaces   The easiest way to create a workspace is to use ready to go stacks in User Dashboard. Images and configuration in these stacks is certified both for Docker and OpenShift, and these are the stacks that are used in daily... </td>
</tr>
<tr><td><a href="env-variables.html">Environment variables</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Environment variables are defined per machine. Depending on the infrastructure, they are added either to container or Kubernetes pod definition. You can add, edit and remove environment variables either in User Dashboard or directly in workspace machine configuration:    <span... </td>
</tr>
<tr><td><a href="environments.html">Workspace Environments</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  </td>
</tr>
<tr><td><a href="installers.html">Installers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  What Are Installers?   Installers are scripts that are injected into machines in a runtime and get executed there to:     Prepare environment and download dependencies for particular software or tool   Install chosen software and dependencies... </td>
</tr>
<tr><td><a href="kubernetes-admin-guide.html">Che on Kuberentes: Admin Guide</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Examples   All examples use kubectl command. OpenShift admins should use oc     RAM   Single User   Che server pod consumes up to 1GB RAM. The initial request is 256MB, and server pod... </td>
</tr>
<tr><td><a href="kubernetes-config.html">Configuration: Kuberentes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  How It Works   Che server behavior can be configured by passing environment variables to Che deployment.   There are multiple ways to edit Che deployment to add new or edit existing envs:     kubectl edit dc/che opens... </td>
</tr>
<tr><td><a href="kubernetes-multi-user.html">Multi-User&#58 Deploy to Kubernetes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Prerequisites     A Kubernetes cluster with at least 4GB RAM and RBAC:   for MiniKube 0.26.0 and above minikube start --cpus 2 --memory 4096 --extra-config=apiserver.authorization-mode=RBAC   for MiniKube 0.25.2 and lower minikube start --cpus 2 --memory 4096 --extra-config=apiserver.Authorization.Mode=RBAC  ... </td>
</tr>
<tr><td><a href="kubernetes-single-user.html">Single-User&#58 Deploy to Kubernetes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td>  Supported Kuberentes Flavors and Versions   Tested only on MiniKube v0.25 with vm providers VirtualBox and kvm2.     Pre-Reqs     bash   Kubernetes installation with:    enabled DNS discovery; ... </td>
</tr>
<tr><td><a href="openshift-admin-guide.html">Che on OpenShift: Admin Guide</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="examples"] == Examples All examples use `kubectl` command. OpenShift admins should use `oc` [id="ram"] == RAM *Single User* Che server pod consumes up to 1GB RAM. The initial request is 256MB, and server pod rarely consumes more than 800MB. A typical workspace will require 2GB. So, *3GB* is... </td>
</tr>
<tr><td><a href="projects.html">Projects</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="projects-in-workspaces"] == Projects in Workspaces Projects are always associated with a workspace and saved in a workspace configuration: [source,json] ---- "projects": [ { "description": "A basic example using Spring servlets. The app returns values entered into a submit form.", "source": { "location": "https://github.com/che-samples/web-java-spring.git", "type": "git", "parameters": {} },... </td>
</tr>
<tr><td><a href="recipes.html">Recipes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="supported-recipe-formats"] == Supported Recipe Formats Depending on the infrastructure, Che supports the following recipes out of the box (default Che build): [cols=",,,,",options="header",] |=== |*Infrastructure* |*Docker Image* |*Dockerfile* |*Composefile* |*Kubernetes yaml* |*Docker* |Supported |Supported |Supported |Not supported |*OpenShift* |Supported |Not supported |Not supported |Supported |=== [id="docker-image"] == Docker Image... </td>
</tr>
<tr><td><a href="secure-servers.html">Secure Servers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :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... </td>
</tr>
<tr><td><a href="servers.html">Servers</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="what-are-servers"] == What Are Servers A server defines protocol port of a process that runs in a machine. It also has a name, path, attributes. Path defines base path of service that is exposed via server. Attributes are optional and may be used to tune server or identify... </td>
</tr>
<tr><td><a href="stacks.html">Stacks</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="what-are-stacks"] == What Are Stacks A stack is a template of link:workspace-data-model.html[workspace configuration] and some meta-information like scope, tags, components, description, name and ID. Stacks are used by User Dashboard to make it easy to create workspaces and well as filter sample projects compatible with a chosen stack.... </td>
</tr>
<tr><td><a href="volumes.html">Volumes</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="default-volumes"] == Default Volumes By default workspace containers/pods start with one default volume/PVC that persists `/projects` where workspace projects are physically located. When a workspace is stopped its machines are destroyed, however, volumes stay there. [id="user-provided-volumes"] == User-Provided Volumes Your workspace may need additional volumes though, say, to... </td>
</tr>
<tr><td><a href="what-are-workspaces.html">What Is a Che Workspace?</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto [id="workspace"] == Workspace Eclipse Che reinvents the definition of a workspace which is usually termed as a local directory with projects and some meta-information that IDE uses to properly configure them. In Eclipse Che, a workspace is the developer environment itself represented by Docker containers, k8s pods or... </td>
</tr>
<tr><td><a href="workspace-data-model.html">Workspace Data Model</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto ---- environments: Map // Workspace envs. A workspace can have multiple envs defaultEnv: STRING // A workspace should have a default environment projects: [] // Projects associated with a workspace commands: [] // Commands associated with a workspace name: STRING // Workspace name that has to be... </td>
</tr>
       <tr><td><a href="workspaces-rest-api.html">Workspace REST API</a></td>
           <!-- <td><span class="label label-default">Page</span></td> -->
         <td> :page-layout: _auto
</td>
       </tr>
<tr><td><a href="workspaces-troubleshooting.html">Troubleshooting Workspace Start Failures</a></td>
    <!-- <td><span class="label label-default">Page</span></td> -->
  <td> :page-layout: _auto Failures to start a workspace may be caused by different factors: 1. Environment recipe 2. Network conditions [id="bad-recipes"] == Bad Recipes When a workspace is being started, environment link:recipes.html[recipe] is sent to Docker or OpenShift API. Che server then listens to events provided by a particular infrastructure. In... </td>
</tr>
   </tbody>
</table>