Chapter 2. New features and enhancements
2.1. Support setting ImagePullPolicy for workspace containers in CheCluster CR
With this update, ImagePullPolicy
for DevWorkspace containers can be now set using the dedicated CheCluster CR field.
apiVersion: org.eclipse.che/v2 kind: CheCluster spec: devEnvironments: imagePullPolicy: <Always|IfNotPresent>
apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
devEnvironments:
imagePullPolicy: <Always|IfNotPresent>
Additional resources
2.2. Adding kubedock to run containers in the UDI
With this update, kubedock is now a part of the UDI (OpenShift Dev Spaces default image). If the environment variable KUBEDOCK_ENABLED
is set to true
in a workspace (this can be done using a devfile), the kubedock server is started at startup.
When KUBEDOCK_ENABLED=true
then the following commands will be executed with kubedock. The remaining commands, in particular, podman build
, will be executed by the local Podman:
-
podman run
-
podman ps
-
podman exec
-
podman cp
-
podman logs
-
podman inspect
-
podman kill
-
podman rm
-
podman wait
-
podman stop
-
podman start
Additional resources
2.3. Configuring default container and pod SecurityContext in CheCluster CR
With this update, the following CheCluster CR fields are available: * spec.devEnvironments.security
* spec.devEnvironments.security.containerSecurityContext
* spec.devEnvironments.security.podSecurityContext
Use the spec.devEnvironments.security.containerSecurityContext
and spec.devEnvironments.security.podSecurityContext`fields to configure the pod and security contexts used by workspaces by setting the corresponding `DevWorkspaceOperatorConfiguration
fields.
If you use the devEnvironments.security.containerSecurityContext
field and devEnvironments.disableContainerBuildCapabilities
is set to false
, the container security context required for the container-builds SCC will be used, overriding the security context set in devEnvironments.security.containerSecurityContext
.
Additional resources
2.4. Using the dedicated ConfigMap to configure the 'Getting Started' samples
With this release, you can configure the 'Getting Started' samples on the User Dashboard by using a dedicated ConfigMap object:
apiVersion: v1 kind: ConfigMap metadata: name: getting-started-sample namespace: openshift-devspaces labels: app.kubernetes.io/part-of: che.eclipse.org app.kubernetes.io/component: getting-started-samples data: my-samples: |- [ { "displayName": "Eclipse Che Dashboard", "description": "Cloud Development Environment for the Eclipse Che Dashboard.", "tags": ["Eclipse Che", "Dashboard"], "url": "https://github.com/eclipse-che/che-dashboard" } ]
apiVersion: v1
kind: ConfigMap
metadata:
name: getting-started-sample
namespace: openshift-devspaces
labels:
app.kubernetes.io/part-of: che.eclipse.org
app.kubernetes.io/component: getting-started-samples
data:
my-samples: |-
[
{
"displayName": "Eclipse Che Dashboard",
"description": "Cloud Development Environment for the Eclipse Che Dashboard.",
"tags": ["Eclipse Che", "Dashboard"],
"url": "https://github.com/eclipse-che/che-dashboard"
}
]
Additional resources
2.5. Navigation from the DevWorkspace Dashboard view to the OpenShift Console DevWorkspace object
Now you can navigate from the Workspace Details
Additional resources
2.6. Customizable OpenShift Dev Spaces logo on User Dashboard
With this update, you can change the OpenShift Dev Spaces logo using the dedicated CheCluster Custom Resource property:
apiVersion: org.eclipse.che/v2 kind: CheCluster spec: components: dashboard: branding logo: base64data: <base64-encoded-data> mediatype: image/png
apiVersion: org.eclipse.che/v2
kind: CheCluster
spec:
components:
dashboard:
branding
logo:
base64data: <base64-encoded-data>
mediatype: image/png
Additional resources