Mounting ConfigMaps

To mount non-confidential configuration data into your workspaces, use Kubernetes ConfigMaps.

Using Kubernetes ConfigMaps, you can mount non-sensitive data such as configuration values for an application.

Mount Kubernetes ConfigMaps to the Dev Workspace containers in the Kubernetes cluster of your organization’s Che instance.

  • An active kubectl session with administrative permissions to the destination Kubernetes cluster. See Overview of kubectl.

  • You have created a new ConfigMap or determined an existing one in your user namespace to mount to all Dev Workspace containers.

  1. Determine an existing ConfigMap in your user namespace to mount to all workspace containers.

  2. Set the required labels for mounting.

    $ kubectl label configmap <ConfigMap_name> \
  3. Optional: Use the annotations to configure how the ConfigMap is mounted.

    Table 1. Optional annotations
    Annotation Description

    Specifies the mount path.

    Defaults to /etc/config/<ConfigMap_name>.

    Specifies how the resource should be mounted: file, subpath, or env.

    Defaults to file.

    mount-as:file mounts the keys and values as files within the mount path.

    mount-as:subpath mounts the keys and values within the mount path using subpath volume mounts.

    mount-as:env mounts the keys and values as environment variables in all Dev Workspace containers.

Example 1. Mounting a ConfigMap as environment variables
kind: ConfigMap
apiVersion: v1
  name: my-settings
  labels: 'true' 'true'
  annotations: env
  <env_var_1>: <value_1>
  <env_var_2>: <value_2>

When you start a workspace, the <env_var_1> and <env_var_2> environment variables will be available in the Dev Workspace containers.