= Add pod placement capabilities for devworkspace-webhook-server and make it more robust With this release, the devworkspace-webhook-server deployment configuration options are available in the global DevWorkspaceOperatorConfig (DWOC) including: [replicas]( https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#replicas), [pod tolerations]( https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/ ) and [ nodeSelector]( https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector ). These configuration options exist in the global DWOC's `config.webhook` field: ```YAML apiVersion: controller.devfile.io/v1alpha1 kind: DevWorkspaceOperatorConfig metadata:   name: devworkspace-operator-config   namespace: $OPERATOR_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]( https://github.com/devfile/devworkspace-operator?tab=readme-ov-file#global-configuration-for-the-devworkspace-operator), 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.