@@ -404,6 +404,10 @@ These values can be specified using [CI/CD variables](../../ci/variables/README.
...
@@ -404,6 +404,10 @@ These values can be specified using [CI/CD variables](../../ci/variables/README.
-`GITLAB_RUNNER_GITLAB_URL` is used for `gitlabUrl`.
-`GITLAB_RUNNER_GITLAB_URL` is used for `gitlabUrl`.
-`GITLAB_RUNNER_REGISTRATION_TOKEN` is used for `runnerRegistrationToken`
-`GITLAB_RUNNER_REGISTRATION_TOKEN` is used for `runnerRegistrationToken`
The methods of specifying these values are mutually exclusive. Either specify variables `GITLAB_RUNNER_REGISTRATION_TOKEN` and `GITLAB_RUNNER_TOKEN` as CI variables (recommended) or provide values for `runnerRegistrationToken:` and `runnerToken:` in `.gitlab/managed-apps/gitlab-runner/values.yaml`. If you choose to use CI variables, comment out or remove `runnerRegistrationToken:` and `runnerToken:` from `.gitlab/managed-apps/gitlab-runner/values`.
The runner registration token allows connection to a project by a runner and therefore should be treated as a secret to prevent malicious use and code exfiltration through a runner. For this reason, we recommend that you specify the runner registration token as a [protected variable](../../ci/variables/README.md#protect-a-cicd-variable) and [masked variable](../../ci/variables/README.md#mask-a-cicd-variable) and do not commit them to the Git repository in the `values.yaml` file.
You can customize the installation of GitLab Runner by defining
You can customize the installation of GitLab Runner by defining
`.gitlab/managed-apps/gitlab-runner/values.yaml` file in your cluster
`.gitlab/managed-apps/gitlab-runner/values.yaml` file in your cluster
