Chapter 2. New features and enhancements 2.1. Add pod placement capabilities for devworkspace-webhook-server and make it more robust With this release, the devworkspace-webhook-server deployment options are available in the global DevWorkspaceOperatorConfig (DWOC) including: replicas , pod tolerations and nodeSelector . These configuration options exist in the global DWOC's config.webhook field: apiVersion: controller.devfile.io/v1alpha1 kind: DevWorkspaceOperatorConfig metadata: name: devworkspace-operator-config namespace: USDOPERATOR_INSTALL_NAMESPACE config: routing: clusterHostSuffix: 192.168.49.2.nip.io defaultRoutingClass: basic webhook: nodeSelector: <string, string> tolerations: <[]tolerations> replicas: <int32> Note In order for the devworkspace-webhook-server configuration options to take effect: You must place them in the global DWOC , which has the name devworkspace-operator-config and exists in the namespace where the DevWorkspaceOperator is installed. If it does not already exist on the cluster, you must create it. You must terminate the devworkspace-controller-manager pod and restart it so that the devworkspace-webhook-server deployment can be adjusted accordingly. Additionally, the default replica count for the devworkspace-webhook-server deployment has been increased to 2 to increase availability. Additional resources CRW-6232 2.2. Warning users that creating a CDE from an unknown source could be dangerous With this release, when you start a cloud development environment (CDE) from a URL, you are asked if you trust the authors of the repository since creating a workspace from unknown or untrusted sources could be dangerous. Additional resources CRW-7120 2.3. Advanced configuration options for the 'Import from Git' flow Starting from this release, it is possible to configure the container image, temporary storage, memory and CPU limits when starting a CDE using the "Import from Git" flow. Additional resources CRW-7121 2.4. Git Configuration from the User Dashboard With this release, you can not only set the name and email for the Git Configuration but also to upload and edit the entire .gitconfig file from the User Dashboard. Additional resources CRW-7122 2.5. Support devWorkspace.ignoredUnrecoverableEvents in the CheCluster CustomResource Starting from this release, you can set ignoredUnrecoverableEvents explicitly on the CheCluster CustomResource level: apiVersion: org.eclipse.che/v2 kind: CheCluster spec: devEnvironments: ignoredUnrecoverableEvents: - FailedScheduling - FailedMount More details about configuring ignoredUnrecoverableEvents can be found in the official documentation . Additional resources CRW-7123 2.6. Add DisableInitContainer field in the Custom Resource The DisableInitContainer field has been added to the CheCluster CR. This field sets the config.workspaces.persistUserHome.disableInitContainer field in the operator-owned DWOC . This field whether the init container that initializes the persistent home directory should be disabled. When the /home/user directory is persisted, the init container is used to initialize the directory before the workspace starts. If set to true, the init container will not be created, delegating the home persistence setup to the CDE's first container component's entrypoint. This field is not used if the devEnvironments.persistUserHome.enabled field is set to false. The init container is enabled by default. Additional resources CRW-7129

Commands:
apiVersion: controller.devfile.io/v1alpha1 kind: DevWorkspaceOperatorConfig metadata: name: devworkspace-operator-config namespace: USDOPERATOR_INSTALL_NAMESPACE config: routing: clusterHostSuffix: 192.168.49.2.nip.io defaultRoutingClass: basic webhook: nodeSelector: <string, string> tolerations: <[]tolerations> replicas: <int32>
apiVersion: org.eclipse.che/v2 kind: CheCluster spec: devEnvironments: ignoredUnrecoverableEvents: - FailedScheduling - FailedMount