GitLab Managed Apps - Runner isn't registered using config from values.yaml file
Summary
The GitLab Managed Apps GitLab Runner documentation suggests that editing /opt/gitlab/embedded/service/gitlab-rails/vendor/runner/values.yaml
would allow you configure the Runner. However, this turns out not to be the case as the Runner is created directly via code instead of registered as per normal.
I had a 100-seat premium customer who wanted (Zendesk, internal use) to their instance-level managed Runner to not take untagged jobs by default. I tried adding runUntagged: false
and tags: "some,tags,here"
to the values.yaml
but these settings did nothing. A little code dive revealed the above findings.
This issue is related to #7983 (closed), but much more specific in nature.
Steps to reproduce
- Edit
/opt/gitlab/embedded/service/gitlab-rails/vendor/runner/values.yaml
withValues.runners.runUntagged: false
- Install GitLab Runner and see that the setting does not take
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
The runner is not created with the specified configuration in the values.yaml
file.
What is the expected correct behavior?
The runner should be created with the specified configuration in the values.yaml
file.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)