### Problem to solve When a group maintainer/owner needs CI/CD runner capacity and no shared runners exist on the instance they should be prompted to create a group runner directly from the group's CI/CD settings. We currently give instructions for how to register the group runner, but we don't make it easy to actually create one. On project CI/CD settings we already provide a button to create a runner on Kubernetes; since we support installing group runners on Kubernetes we should also provide a button to do so from the group's CI/CD settings page. Need statement: **The user** needs a way to **to become aware of the availability of group runners for Kubernetes when no shared runners exist for the instance** so that they can **provision GitLab runners across multiple projects easier.** ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> Our current setting pages look like this, which are the only places the user is suggested to create a runner (except for the Kubernetes cluster page). | Current project CI/CD settings | Current group CI/CD settings | | ------ | ------ | |  |  | ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> 1. A button and area similar to the project CI/CD settings, on the group CI/CD settings page. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references