Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9789

Closed
Open
Created Oct 30, 2015 by Administrator@rootOwner

Ability for scaling runners into a cluster, by allowing a configuration of the REGISTER_TOKEN.

Created by: cusspvz

We are trying to deploy runners (using gitlab-ci-multi-runner) into our dev cluster, happens that we have 4 gitlab instances into the GitLab service and all of them have different runner register tokens.

When we deploy a gitlab-ci-multi-runner service, we cannot know which GitLab instance runner will hit. (In fact we could, but it won't meet our HA scheme standards since scaling would fail in case that specific GitLab instance goes down, and a Health Check failure is enough to replace that failing instance by a new one).

As so, I'm proposing to add a config statement for the REGISTRATION_TOKEN constant. I can also contribute with a PR if the GitLab Team agree with the proposal.

Thanks, José Moreira

Assignee
Assign to
Time tracking