Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,887
    • Issues 34,887
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,214
    • Merge Requests 1,214
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #29706

Closed
Open
Opened Jun 26, 2019 by Mark Pundsack@markpundsackContributor

Prompt to install group runner on Kubernetes

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

Devon (DevOps Engineer)

Further details

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
image image

Proposal

  1. A button and area similar to the project CI/CD settings, on the group CI/CD settings page.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

Links / references

Edited Jul 30, 2019 by Jason Yavorska
Assignee
Assign to
12.4
Milestone
12.4 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#29706