<p>I am having a problem with a helm deployment of GitLab onto my kubernetes cluster.  Everything was working except for the GitLab Runner that was throwing the error:</p>
<pre><code>ERROR: Registering runner... forbidden (check registration token)
PANIC: Failed to register this runner. Perhaps you are having network problems 
</code></pre>

Antebios
<p>The solution to this was the <code>gitlab-gitlab-runner-secret</code>.</p>
<p>Data element: runner-registration-token</p>
<p>value: FGvuUvo0aAce2xkLjvWxj1ktGHD8NAzWY4sLYDVvD3Z56JXh2E7rwfaTvKGkRlUJ</p>
<p>It was pre-populated with an invalid  <code>runner-registration-token</code>.  I solved this by:</p>
<ol>
<li>Going to GitLab Admin Area --&gt; Runners</li>
<li>In the section &quot;Set up a shared Runner manually&quot;, copy the <code>registration token</code>.</li>
<li>On a bash command line encode the string to base64 with the command:</li>
</ol>
<pre><code>echo &lt;my_registration_token&gt; | base 64
</code></pre>
<ol start="4">
<li>Copy the output value and go Edit the kubernetes secret for <code>gitlab-runner-secret</code>.</li>
<li>Paste the encrypted value OVER the existing value, then click the Update button to save changes.</li>
<li>Now stop/destory the runner pod OR scale the deployment to zero destroy it and scale the deployment back up to 1.</li>
<li>Now you will see the GitLab Runner pod finally running properly with the log showing:</li>
</ol>
<pre><code>Registering runner... succeeded
Runner registered successfully.
</code></pre>
