sameersbn / sameersbn/docker-gitlab
token generation for kubernetes automation
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
When the server restarts the token for gitlab runners appears to be regenerated.
It would be preferable to specify the the token in an environment variable for the replication controller / pod for the gitlab instance that can be shared with the runners.
Is there an option / way to do this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the Dockerized GitLab server generates the GitLab Runner token during a restart and how the replication controller or pod receives environment variables. Verify whether an existing configuration entry point supports a supplied token, then test that the token remains shared with runners after restart. The issue names no files or tests, so locating the relevant configuration will require repository research.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100