Allow or disallow particular Runner configurations in GitLab
Release notes
In organisations that let different teams set up and manage their own (group) runner fleets, misconfigurations can have disproportional performance impact on the shared Gitlab instance, and may be hard to track down and resolve.
Problem to solve
GitLab admins can not currently prevent certain undesired runner configurations to be used, or prescribe certain desired configurations.
Proposal
- Implement a mechanism that lets Runner upload its
config.tomlto GitLab. - Implement allow/disallow lists in the GitLab admin interface.
- Implement rejection and/or overwriting logic.
Alternative
Improving the utility of config.toml templates, see for example:
Related
- gitlab-runner!3414 (merged) (more changes like this will limit which runner versions can be registered on newer instances)
- gitlab-com/marketing/digital-experience/buyer-experience!766 (closed) (policy change discussed within support)
Intended users
- Cameron (Compliance Manager)
- Sidney (Systems Administrator)
- Alex (Security Operations Engineer)
- Ingrid (Infrastructure Operator)
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.