Update runner manager term based on user feedback
Details
In https://gitlab.com/gitlab-org/ux-research/-/issues/2444#what-did-we-learn, we learned that users were not able to define most of the runner terminology accurately, based on the definitions we have internally. We also learned from ux-research#2561 (closed) that users most commonly use runner manager for automatically managing runner resources in order to optimize job performance. This does not match how we currently use runner manager today, as we refer to these as the machines linked to the runner configuration today.
- How users defined it: autoscaler, resource scaler, runner manager
- Terms users matched to it: runner manager, controller
Proposal
- Update
ci_runner
torunner_configuration
- Update runner manager definition to be A tool that automatically adjusts the resources allocated for a particular unit of work needed to support an application of service. in the glossary. (Currently is
A type of runner that can create multiple runners for autoscaling. Specific to the type of executor used.
) - Update
runner_manager
to be runner.
Out of scope for this issue
- Update the runner creation workflow to make it clear you are first creating a runner configuration and then linking runners to this.