Identify registered gitlab-runner on kubernetes


I have gitlab-runner instance on my gcloud kubernetes, but there’s a problem when the pod is restarted. After restart, my runner always get new runner token, and there is no configuration from before restart.
In helm chart values.yml there is runnerToken parameter, but in description is information, that there is no documentation yet for that. When I paste here token from existing gitlab runner, my pod doesn’t start, and returns crashLoopBackOff.

Is that possible, to always run gitlab-runner on kubernetes with the same runner token?

1 Like