Devfile has been incubated by Eclipse Che project providing devfile v1 specification.

To allow other projects to use a common definition, devfile has moved out of Eclipse Che. It has its own definition at with current v2.1.0 specification.

Devfiles v1 were handled by Eclipse Che Server workspace engine using Java/Kubernetes API. There is a new engine for v2 Devfiles called DevWorkspace Controller. The source code is at:

DevWorkspaces are custom Kubernetes resources and can be created/listed/deleted using any Kubernetes client like kubectl.

A DevWorkspace is a workspace using the new engine and supporting Devfile v2 definition.


Devfile v2 support in Eclipse Che can be followed by milestones.

  • Milestone 1 introduced the first support of Devfile v2 (start a basic workspace)
  • Milestone 2 just landed in Eclipse Che 7.32.0 with the support of Theia plug-ins for DevWorkspaces
  • End Game is the End Game issue.

How to test ?

The support of Devfile v2/DevWorkspaces is optional and need to be opt-in.

When the support is enabled, both Devfile v1 and v2 are supported. You can still work with your previous workspaces and Devfile v1.

  • If the devfile.yaml has apiVersion 1.0.0, it will use Che server workspace engine to deploy this Devfile.
  • If the devfile.yaml has schemaVersion 2.0.0 (or greater like 2.1.0), it will use the DevWorkspace controller to deploy this Devfile.

⚠️ DevWorkspaces requires OpenShift as platform until Milestone 3 is reached (vanilla Kubernetes is not supported yet)

ℹ️ When DevWorkspace is enabled, single-host deployment is enforced. As a consequence, when the Che host certificate is untrusted, there is no need to locally install it.

To enable DevWorkspaces, use a custom spec object for Che Operator:

Creates a file in your ${HOME} folder for example ${HOME}/enable-devfilev2.yaml with the following content:

    enable: true

Install Eclipse Che (latest stable ≥7.32 or next channel) with chectl:

$ chectl update next # (or stable)  
$ chectl server:deploy --che-operator-cr-patch-yaml=${HOME}/enable-devfilev2.yaml

Then, search for the Dashboard link in the chectl output:

✔ Eclipse Che 7.33.0-SNAPSHOT has been successfully deployed.  
  ✔ Documentation        : [](  
  ✔ -------------------------------------------------------------  
  ✔ Users Dashboard      :  
  ✔ -------------------------------------------------------------  

Opening the Dashboard page will display the new getting started:

Getting Started

Clicking on a sample will use a Devfile v2 and the DevWorkspace engine.

ℹ️ The installation guide is also available in Eclipse Che documentation

Updating from Devfile v1

While the syntax between v1 and v2 yaml definition is close, there is a major change in the DevWorkspace definition: the IDE plug-ins are no longer part of the Devfile.

It brings more clarity: for example, it was possible to include a java plug-in but it was unclear that it required the Eclipse Theia editor and that it would not work with other supported editors. Also, when the Devfile was consumed by other tools like odo that don’t have the notion of plugin or editor, those components were ignored.

Another change in the lifecycle of a workspace is that the project clone operation is done by the DevWorkspace engine. So whatever Che editor is picked-up, the project will always be cloned in /projects/<your-project> location after the workspace start (no matter if there is an editor/IDE or not).

Plug-ins definition

IDE preferences

While IDE plug-ins are no longer part of the devfile.yaml, instead or reinventing a new file format to specify an IDE plugins, the idea was to leverage the already existing definition files.

For example VS Code has .vscode/extensions.json file where plug-ins can be recommended.

Eclipse Che now supports this file format and, when it founds one and the editor is Eclipse Theia, it will add the corresponding VS Code extensions to the DevWorkspace.


  "recommendations": [

in .vscode/extensions.json will automatically install redhat/java VS Code extension in the Eclipse Che workspace.

Note: if the specified set of extensions IDs are not available in the Eclipse Che plug-in registry, the workspace creation won’t fail but the extensions won’t be included.

The list of the VS Code extension that can be included in a Che Theia workspace are available on the online registry at The registry is continuously updated when PRs get merged on Che plugin registry main branch.

Custom definition

Relying on .vscode/extensions.json is great but, to run a VS Code extension as a Kubernetes workload, may require some extra specifications that are not part of this file format.

Here comes the .che/che-theia-plugins.yaml optional file.

For example, overriding some container settings like the memoryLimit for the plug-in.

- id: redhat/java  
      memoryLimit: 2Gi


Sometimes it may not be possible to include the files .vscode/extensions.json or the .che/che-theia-plugins.yaml in the git repository.

Inlining the content of these files in the devfile.yaml file is somehow possible using the following syntax of the Devfile:

schemaVersion: 2.1.0  
  name: my-example  
  .vscode/extensions.json: |  
      "recommendations": [  

To inline .che/che-theia-plugins.yaml :

schemaVersion: 2.1.0  
  name: my-example  
  .che/che-theia-plugins.yaml: |  
    - id: redhat/java

Workflow of handling IDE plug-ins with workspaces

devfile v2 workflow

New Features for plug-ins

Although excluding the IDE plug-ins from the Devfile specification represents a big change, each editor can now bring new features more easily. Each editor can directly update a workspace using DevWorkspaceTemplate objects based on its configuration files (like optional .vscode/extensions.json or .che/che-theia-plugins.yaml files).

Deploy plug-ins in existing containers

By default, in Eclipse Che and when using Eclipse Theia editor, IDE plug-ins were deployed either in the Che-Theia container (when it only requires nodejs runtime) or through a new sidecar container (for example for Java, Go, Python, Php, etc.)

In that case, all plugins requiring a sidecar will be deployed in the user defined container and not in their specific sidecar container.


If a repository contains these two files:

  1. devfile.yaml with the following content:
    schemaVersion: 2.1.0  
      name: my-example  
      - name: tools  
       command: ['tail']  
       args: ['-f', '/dev/null']
  2. And the file .vscode/extensions.json containing

The plug-in will be started inside the tools container and in its own sidecar container.

For this to work the tools container should include the plug pre-requisites otherwise the VS Code java extension will fail to start.

To disable this behaviour, use the following attribute:

attributes: mergeImage

Prebuilt DevWorkspace templates

With Devfile v1 the flow was the following: a user selects a getting started example, the Dashboard fetches the Devfile, the plug-in broker analyzes the devfile.yaml fetches the content from linked plug-in registries, parses the meta.yaml of these plug-ins, extracts the sidecar containers definitions and, finally, adds some containers to the workspace definition.

With Devfile v2, these steps with a lot of yaml/json transformations are still present but the output result is a set of DevWorkspace templates that will be applied on the Kubernetes cluster.

Those DevWorkspace templates can be generated at build time rather than at runtime. The Che-Theia library, with a Devfile provided as input (the optional .vscode/extensions.json and .che/che-theia-plugins.yaml files), generates a yaml file that includes the definition of the DevWorkspace templates.

npx @eclipse-che/che-theia-devworkspace-handler –devfile-url: –output-file:$(pwd)/all-in-one.yaml

Then this file can be used directly by kubectl :

kubectl apply -f all-in-one.yaml -n my-namespace

These templates can be included in the Devfile registry and the Eclipse Che Dashboard will apply them directly instead of processing the original Devfile at every workspace start.

Plug-in registry changes

For workspaces using Devfile v1, Eclipse Che server fetches a meta.yaml files from the plug-in registry. There are some limitations, for example defining plug-in preferences is only possible if there is a sidecar being defined, etc.

With DevWorkspaces, the plug-in registry export now the content provided in different formats. It still exports meta.yaml files but it also exposes devfile.yaml files for Eclipse Che editors definition and for some plug-ins that are not IDE plug-ins like che-machine-exec (library to be able connect to a specific container in a workspace/pod).

Also the Che-Theia IDE plug-ins are now exposed by their che-theia-plugin.yaml fragment.

Every Che-Theia plug-in fragment is generated from the che-theia-plugins.yaml file.

An hosted version of the che-plugin-registry is available after each commit at

Corresponding definition forredhat/java IDE plug-in is available at:

It references the dependencies of this IDE plug-in and its preferences (whereas with meta.yaml the notion of dependency didn’t exist and all the required .vsix had to be specified in the file)

  java.server.launchMode: Standard  
  - vscjava/vscode-java-debug  
  - vscjava/vscode-java-test

Eclipse Che Devfile registry changes

The index of the Devfile registry is providing a list of Devfiles to use. But now, Devfile v2 as some other optional files may be required, it’s better to reference a repository rather than a single devfile.yaml.

New links are available in the Devfile registry. The v2 links are links to either repositories or devfiles.

Here is an example of a minimal index of a Devfile registry:

  "displayName": "Java Spring Boot",
  "icon": "/images/springboot.svg",
  "links": {
    "v2": "",
    "self": "/devfiles/java-web-spring/devfile.yaml"

If the DevWorkspaces is enabled and there are some v2 links in the Devfile registry, only Devfile v2 getting started will be shown on the Dashboard (Devfile v1 getting started will be hidden). Each of these samples will use the new DevWorkspace engine.

Getting Started

In addition to those changes, there is an ongoing effort to merge Che Devfile registry and community Devfile registry. This work is part of the Devfile project that is planned to become a CNCF sandbox project.