<p>After performing some experiments: <strong>Yes, worker nodes need access to the GitLab instance.</strong> (At least on GitLab Runner 14.)</p>
<p>The Runner Manager will just spawn the workers and communication happens directly between the workers and the GitLab instances. When the workers cannot access GitLab, you'll probably see an error message like:</p>
<pre><code>fatal: unable to access 'https://your.gitlab.instance/awesome/project.git/': Could not resolve host: your.gitlab.instance
</code></pre>

CC BY-SA 4.0
2021-10-19T09:33:45.463Z
2021-10-19T09:33:45.463Z
Moritz
<p>GitLab runner has an <a href="https://docs.gitlab.com/runner/configuration/runner_autoscale_aws/" rel="nofollow noreferrer">autoscale feature</a> that allows the Runner Manager to dynamically spawn new worker nodes on demand.</p>
<p>The documentation says that: &quot;GitLab Runner is going to need to talk to your GitLab instance over the network&quot;. This is obvious to me since the runner needs to download the source code and push build results and artifacts back to GitLab.</p>
<p>Is this required for the Runner Manager only or also for its worker nodes? Do the nodes communicate with GitLab directly or do they only talk to the Runner Manager, which then propagates their results to GitLab?</p>
<p>In other words: With a GitLab instance in my private corporate network and autoscaling GitLab Runner with AWS EC2, do I need to build a VPN between my corporate network and AWS VPC or will it work out of the box?</p>

<amazon-web-services><gitlab><cicd><gitlab-ci-runner><autoscaling>
Do GitLab Runner worker nodes need to have network access to GitLab?
Moritz
# Do GitLab Runner worker nodes need to have network access to GitLab?

(Asked by: username_0 on 2021-10-07)

GitLab runner has an [autoscale feature](https://docs.gitlab.com/runner/configuration/runner_autoscale_aws/) that allows the Runner Manager to dynamically spawn new worker nodes on demand.

The documentation says that: "GitLab Runner is going to need to talk to your GitLab instance over the network". This is obvious to me since the runner needs to download the source code and push build results and artifacts back to GitLab.

Is this required for the Runner Manager only or also for its worker nodes? Do the nodes communicate with GitLab directly or do they only talk to the Runner Manager, which then propagates their results to GitLab?

In other words: With a GitLab instance in my private corporate network and autoscaling GitLab Runner with AWS EC2, do I need to build a VPN between my corporate network and AWS VPC or will it work out of the box?

**Tags:** amazon-web-services, gitlab, cicd, gitlab-ci-runner, autoscaling


---

## 1 answers

### Answer by username_0 on 2021-10-19. Score: 1

After performing some experiments: Yes, worker nodes need access to the GitLab instance. (At least on GitLab Runner 14.)
The Runner Manager will just spawn the workers and communication happens directly between the workers and the GitLab instances. When the workers cannot access GitLab, you'll probably see an error message like:
fatal: unable to access 'https://your.gitlab.instance/awesome/project.git/': Could not resolve host: your.gitlab.instance


---

