Gitlab Runner Integration with Gitlab
-
Gitlab Runners are not deployed as part of CI testing. -
Gitlab Runners don't connect to Gitlab by default.
Per the Gitlab docs, you can provide a secret to gitlab: (copied from chart/docs/install/secrets.md)
GitLab Runner secret
Replace <name>
with the name of the release.
kubectl create secret generic <name>-gitlab-runner-secret --from-literal=runner-registration-token=$(head -c 512 /dev/uran
and then referencce the secret in
global:
## GitLab Runner
## Secret created according to doc/installation/secrets.md#gitlab-runner-secret
## If allowing shared-secrets generation, this is OPTIONAL.
runner:
registrationToken: {}
# secret:
In GitlabRunners:
runnerRegistrationToken: ""
We need to identify:
- Provide an API to pass in this secret value and create the secret in Gitlab and then configure Gitlab Runners to use it
- Autogenerate a secret token to create secret, but ensure that we don't re-create this value each time helm deploys.
- Pass the secret token to gitlab runners in the
secret
Values so its not visible in the HelmRelease.
Edited by runyontr