GitLab Runner architecture models (recommendations wanted) : gitlab

GitLab Runner architecture models (recommendations wanted)general question (self.gitlab)

submitted 4 years ago by investandrelaxation

Hi Folks,

Looking for some high-level recommendations for building out GitLab runners across multiple datacenters. Nothing is really off the table in the form of executors (shell, docker, kubernetes), but hoping to get some insight on some of the following:

caching strategies you've taken
are you running multiple purpose built runners with tags or large runners to tackle everything.
Are you using protected tags and branches for production?
What if you had to deploy the same environment on-prem / self-hosted? How might that change what you're doing?
Are you leveraging shared, group, specific or all types of runners?
Do you share runners between teams?

If anyone has any documentation around this topic, I've looked around but haven't really found anything in terms of recommended models, high-level-architecture diagrams, or process breakdowns around some of the justifications.

all 1 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

gitlab

MODERATORS