Skip to content

README.md

Latest commit

 

History

History
38 lines (29 loc) · 1.61 KB

README.md

File metadata and controls

38 lines (29 loc) · 1.61 KB
Raw

Intro

In this document I'll explain how did I separate the omnibus gitlab build to multiple services.

I followed the guides to make the service to be compatible with 2K users. More details can be found here https://docs.gitlab.com/ee/administration/reference_architectures/2k_users.html

Add More Workers

To add more workers we have a few components that need to be edited:

  • Increase the scale field in gitlab service.
  • For each scaled container, docker-compose adds _(int) extension to container name. once you will increase the scale field, you will get another gitlab_gitlab_3 for example.
  • In ingress service you should edit external_links field and add the new mapped service.
  • In nginx.conf - you should add the new service to the following upstreams:
    • load_balancer_http
    • load_balancer_https
    • load_balancer_ssh
  • Once all configured, run start.sh again and the components will get updated

Open Issues

  • HTTPS certificate
  • Backups

Migration

The migration from omnibus config to this running setup should include several changes:

  • Change the mounts according to your correct omnibus setup (see GITLAB_DATA_FOLDER in config.dev for more details per service in the compose files).
  • Copy config.template.env and populate the values acording to the right setup.
  • Copy gitlab-secrets.json and the host SSH keys from the gitlab config directory.

First time sample run

  • You should consider if you even want to use those compose files and not just run the omnibus setup
  • If you still consist, the setup should go up out of the box, but it takes time, so be patient.