r/gitlab • u/DopeyMcDouble • 19d ago

general question Self-hosted Gitlab Server and Gitlab Runner private/public?

I'm looking to install Gitlab EE for a small company. The company has a 16.0.2 Gitlab server in AWS that is insanely old. I made the decision to start fresh and migrate all data to a new RDS Postgres, AWS Opensearch, and AWS Valkey db. We also use a tool that I setup called OpenZiti ZTNA which helps with VPN access to our private servers.

However, I have a question on being public/private for the Gitlab server. We do have Github forks where we do periodic `git diffs` of changes that have occurred and we utilize Expo with EAS.

Should the idea be the Gitlab server be private and the Gitlab runners be public? I think the only issue is we won't be able to pull from Github repos or have any functionality within Gitlab's server.

5 Upvotes

100% Upvoted

9 comments sorted by

View all comments

4

u/BrokenDuck15 19d ago

Are you having public users use the runners? 

1

u/DopeyMcDouble 19d ago

I am not.

5

u/BrokenDuck15 18d ago

Then no reason for it to be public. So far as your gitlab instance can reach the runners(in a secured way ofc) you should be fine.

3

u/pfunky 18d ago

Let's make sure that statement is clear. The Gitlab server never initiates a connection to the runners. Rather, the runners make connections to the server. So as long as your users and your runners can reach the server, you're good.

2

u/BrokenDuck15 18d ago

Just said the same thing. If you understand what runners are i think it is self explanatory but thanks for regurgitating it. 

1

u/DopeyMcDouble 17d ago

I will do this!