UX concept for custom-hosted runners
This issue is supposed for the UX concept of how users will create, monitor and interact with Dedicated Runners.
The Idea is to use the capabilities of ~"Category:Runner Fleet" and integrate the workflow for custom runners there.
Adding a new Runner
To add a new runner, users should use the same workflow as self-managed runners under Settings > CI/CD > Runners > Create new hosted runner
The creation screen should be adapted to reflect the choices users have for a dedicated runner. This would be the selection of OS, runner name, tags, details next to some other features we intend to deliver for these runners such as the option for static IP range of scaling parameters the user would be able to control.
The benefit of using this screen is a seamless workflow for users and the same screen independent of self-managed or hosted runners.
Mockup:
Managing a Runner
The new registration token architecture would also allow users the same control for dedicated runners as with self-managed. They can easily decide what groups or projects, a dedicated runner should be connected to.
Monitor a Runner
Users request a better overview and insight into dedicated runners. For this, we plan to use the Runner Fleet Dashboard and extend it for Groups and Projects.
Using this Dashboard would provide a lot of insights to the runner fleet without having to leave GitLab.
In the next iteration, we could add Cost Visibility to the dashboard. I wrote down all my thoughts on the future of compute minutes here.