<p>I have a gitlab runner build by helm on GKE, I had registration this runner.</p>

<p>When I trigger my pipelines, runner run failed and got this error</p>

<pre><code>Running with gitlab-runner 11.7.0 (8bb608ff)
  on gitlab-runner-gitlab-runner-5bb7b68b87-wsbzf -xsPNg33
Using Kubernetes namespace: gitlab
Using Kubernetes executor with image docker ...
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Waiting for pod gitlab/runner--xspng33-project-3-concurrent-0rsbpp to be running, status is Pending
Running on runner--xspng33-project-3-concurrent-0rsbpp via gitlab-runner-gitlab-runner-5bb7b68b87-wsbzf...
Cloning into '/general/year-end-party/yep-web'...
Cloning repository...
fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitlab.shopee.nctu.me/general/year-end-party/yep-web.git/': SSL certificate problem: unable to get issuer certificate
/bin/bash: line 72: cd: /general/year-end-party/yep-web: No such file or directory
ERROR: Job failed: command terminated with exit code 1
</code></pre>

<p>I saw many solutions say I could set ssl_verify false.
But my runner is installed by helm, I didn't touch runner's config.toml.
I don't know how could I solve this. Please help me.</p>

<p>I also had add cert for runner
<a href="https://i.stack.imgur.com/51wLt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/51wLt.png" alt="enter image description here"></a>
<a href="https://i.stack.imgur.com/wOug8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/wOug8.png" alt="enter image description here"></a></p>

Rukeith
<p>You need to create a Kubernetes Secret with the content of your certificate in the namespace of your gitlab-runner. The secret will be used to populate the /etc/gitlab-runner/certs directory in the gitlab-runner. </p>

<p>After that, you need to <a href="https://docs.gitlab.com/ee/install/kubernetes/gitlab_runner_chart.html#configuring-gitlab-runner-using-the-helm-chart" rel="nofollow noreferrer">refer</a> the secret name in your values.yaml helm chart :</p>

<pre><code>## Set the certsSecretName in order to pass custom certficates for GitLab Runner to use
## Provide resource name for a Kubernetes Secret Object in the same namespace,
## this is used to populate the /etc/gitlab-runner/certs directory
## ref: https://docs.gitlab.com/runner/configuration/tls-self-signed.html#supported-options-for-self-signed-certificates
##
 certsSecretName: &lt;name_of_your_secret&gt;
</code></pre>

<p>More info in the <a href="https://docs.gitlab.com/ee/install/kubernetes/gitlab_runner_chart.html#configuring-gitlab-runner-using-the-helm-chart" rel="nofollow noreferrer">gitlab</a> documentation.</p>
