Currently, on a multi-node cluster, it is not possible to specify which node(s) to have the devworkspace webhook server scheduled onto. It'd be great to dedicate specific nodes on a cluster to running the webhook server using Kubernetes labels & taints. These dedicated nodes could minimize the amount of downtime & latency experienced for the webhook server, which is critical given that all exec's on the cluster will trigger the validating webhook (see https://github.com/devfile/devworkspace-operator/issues/796).
This could be accomplished by allowing the configuration of nodeSelectors and tolerations for the webhook server.
Description
Currently, on a multi-node cluster, it is not possible to specify which node(s) to have the devworkspace webhook server scheduled onto. It'd be great to dedicate specific nodes on a cluster to running the webhook server using Kubernetes labels & taints. These dedicated nodes could minimize the amount of downtime & latency experienced for the webhook server, which is critical given that all exec's on the cluster will trigger the validating webhook (see https://github.com/devfile/devworkspace-operator/issues/796).
This could be accomplished by allowing the configuration of nodeSelectors and tolerations for the webhook server.
Additional context
Downstream issue: [CRW-6232] Add pod placement capabilities for devworkspace-webhook-server and make it more robust