This section describes the properties of the Che server that affect the provisioning of a Che workspace.

Persistent volume configuration

A Kubernetes persistent volume is attached to the Che workspace to persist its data: source code, application logs, and tools configuration. A Che server can be configured to use different strategies:

  • common: A Che workspace that is provisioned in the same Kubernetes namespace and shares the same PersistentVolume. The data of different workspaces are separated using subpaths. The default strategy is common.

  • unique: Every Che workspace is attached to a distinct persistent volume. This strategy provides better data isolation but requires more resources.

Workspace namespaces configuration

The Kubernetes namespace where a new workspace pod is deployed depends on the Che server configuration. By default, every workspace is deployed in a distinct namespace, but the user can configure the Che server to deploy all workspaces in one specific namespace. The name of a namespace must be provided as a Che server configuration property and cannot be changed at runtime.