Enable feature flags for new runner creation
What does this MR do and why?
🎉
Enable feature flags for new runner creation This change enables the new runner creation workflow in which users can create runners and use a runner authentication token to register them to their GitLab instance.
This eliminates the need for a registration token.
Runner creation happens in the GitLab Runners settings page for the given scope, in the context of the authenticated user, which provides traceability.
See more at: https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/#next-gitlab-runner-token-architecture
See more about our documentation at: https://docs.gitlab.com/ee/ci/runners/register_runner.html
Changelog: added
Screenshots or screen recordings
How to set up and validate locally
Admin area:
- Visit Admin -> CI/CD -> Runners
- Select New instance runner (e.g. http://gdk.test:3000/admin/runners/new)
- Follow the runner registration process
Group and Project area
-
Visit your group's home, Group -> CI/CD -> Runners
-
Select New group runner (e.g. http://gdk.test:3000/grou/runners/new)
-
Follow the runner registration process
-
Visit your project's home, Settings -> CI/CD
-
Expand Runners, select "New project runner"
-
Follow the runner registration process (e.g. https://gitlab.com/runner-group-test/test-project/-/settings/ci_cd)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #389269 (closed)