Better way to see and control your GitLab self-hosted runners.
493
Better way to see and control your GitLab self-hosted runners.
Main documentation of GitLabKit Runner Admin can be found here
1, 1.1, 1.1.0, latest1.0, 1.0.11.0.0pr-<pr-number> ex. pr-10Example docker run command with minimal settings
$ docker run \
-e CONNECTIONS__GITLABSERVER="https://<your-gitlab-server>" \
-e SECRETS__GITLABTOKEN="<gitlab-token>" \
-e CONNECTIONS__REDISSERVER="<redis-host>" \
-p 80:80 \
encx/gitlabkit-runner
| variable | example | required | description |
|---|---|---|---|
CONNECTIONS__GITLABSERVER | https://gitlab.yourcompany.com | yes | GitLab server URL |
SECRETS__GITLABTOKEN | rG2f93ddaz | yes | GitLab token. Could be a personal token or group token that has sufficient permission to view CI/CD settings in the group |
CONNECTIONS__REDISSERVER | redis-server:16379 | no | Redis host. If set, it will be used as cache. |
SECRETS__REDISUSER | username | no | Redis ACL user. Leave empty if Redis has no ACL user set. |
SECRETS__REDISPASSWORD | password | no | Redis password. Could be used alone if Redis has set requirepass. Or could be used together with SECRETS__REDISUSER for ACL authentication. |
LOGTARGETS__SEQ | http://seq-server:5341 | no | Runner Admin supports Seq logger. Use this to set log ingestion URL. |
APPLICATIONINSIGHTS__CONNECTIONSTRING | - | no | Runner Admin supports Application Insights to see application diagnostics. Use this to set connection string from Azure dashboard. |
80. Yeah, that's it.
Content type
Image
Digest
Size
87.2 MB
Last updated
over 4 years ago
docker pull encx/gitlabkit-runner