<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=490984) </details> <!--IssueSummary end--> ### Proposal In the agent configuration file located at `/.gitlab/agents/<agent-name>/config.yaml`, it would nice to be able to add an additional parameter with a structure like this: ``` remote_development: enabled: true gitlab_workspaces: nodeSelector: gitlab-ws-nodes ``` We would then use this value in the Workspaces deployments, as outlined here: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector With this approach, we can manage a separate node pool for Workspaces based on the `nodeSelector`. For example, we could assign t3 nodes for developers and c7 nodes for EKS runners. This setup would also allow us to deploy different agents that use different nodes — one for development and another for executing more resource-intensive tasks such as tests or analysis.