we are using GitLab runner on k8s installed with helm chart (quite old - still with a tiller so Helm 2 based). Currently the config.toml file has the following content (taken from k8s ConfigMap):
since you mentioned Helm v2, I did not want to point you directly to the latest head. Instead, the Git history hides the source of the Helm chart’s default configmap:
Looking at it, and digging deeper into the repository, I can see the values.yaml you can override.
That being said, chart versions 0.23.0+ allow to specify a custom config template for the runner. 0.27.0 adds a configmap override. More advanced configuration is described in the docs.
In your release, you are limited to the static value mapping between values.yaml and configmap.yaml defined by the Helm chart itself. There are workarounds discussed in the linked MRs with a custom Docker image for deployments. I would not go there though but instead upgrade the chart, and test the different versions and configuration options.
thanks for your help and recommendations.
We are not using a custom docker image - just the standard one:
gitlab/gitlab-runner:alpine-v12.10.2
I am still trying to understand how the runners.Kubernetes.volumes.host_path gets added to the config.toml file.- is it hardcoded in the runner binary file?