## Overview In GitLab Runner 13.10.0 we introduced https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/2739 which adds support for graceful termination for the Windows shared runners, which is one of the things blocking us from doing more frequent deployments in the Windows shared runner fleet. ## Proposal - [x] Update the GitLab Runner version in https://ops.gitlab.net/gitlab-com/gl-infra/ci-infrastructure-windows/-/blob/c065a7aa04c958ffe941c0a80fbd4dba592e0c1a/ansible/group_vars/gcp_role_runner_manager.yml#L1 :point_down: https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12790#note_545056565 (done) - [x] Set `FF_USE_WINDOWS_LEGACY_PROCESS_STRATEGY` to `false` through [runner environment variables](https://docs.gitlab.com/runner/configuration/feature-flags.html#enable-feature-flag-in-runner-environment-variables) - [ ] Update the [ansible apply](https://ops.gitlab.net/gitlab-com/gl-infra/ci-infrastructure-windows/-/blob/master/.gitlab/ci/40_apply.gitlab-ci.yml) to first run `gitlab-runner stop` on 1 node and then run the ansible apply. This should be done 1 node at a time to prevent any downtime. - [ ] Update [the documentation](https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/ci-runners/windows/README.md#graceful-shutdown-of-windows-runner-managers) about handling Graceful Shutdown on Windows Runner Managers.