## Summary The current runner fleet serving the `gitlab--duo` CI tag uses the **docker+machine** executor, which is a legacy executor that does not support the suspend/resume functionality being developed as part of [Resumable Jobs for CI and Agent Sessions](https://gitlab.com/groups/gitlab-org/-/work_items/21159). To unblock the AI/DAP teams from using resumable jobs, a new dedicated runner fleet must be provisioned using a modern executor that supports suspend/resume semantics. ## Background Resumable Jobs (suspend/resume) is being implemented for the following modern executors: - **Instance Autoscaler** (via Fleeting + Taskscaler) - **Docker Autoscaler** (via Fleeting + Taskscaler) - **Kubernetes** (planned, with gVisor isolation) e requirement for interactive agent sessions and human-in-the-loop workflows. ## Proposal Provision a new dedicated runner fleet for the `gitlab--duo` tag using one of the following modern executors: 1. **Docker Autoscaler** (alternative, already supported in the suspend/resume spike) 1. **Instance Autoscaler** (alternative, already supported in the suspend/resume spike) 1. **Kubernetes executor** ( — allows gVisor isolation, simpler orchestration delegation to the Kubernetes control plane) ## References´ - Discussion thread raising this need: https://gitlab.com/groups/gitlab-org/-/work_items/21159#note_3189325736