GitLab Dedicated Architecture

GitLab Dedicated Group logo

Architecture

This page collects a set of architectural documents and diagrams for GitLab Dedicated.

High level overview

High level overview diagram for GitLab Dedicated

Tenant network

Tenant network diagram for GitLab Dedicated

Gitaly Setup

GitLab Dedicated deploys Gitaly in a sharded setup, not a Gitaly Cluster. In this setup:

  • Customer repositories are spread across multiple virtual machines.
  • GitLab manages storage weights on behalf of the customer.

Geo Setup

GitLab Dedicated leverages GitLab Geo for Disaster Recovery.

Note: GitLab Geo is not an “active/active” system. To learn more about how GitLab Geo works, see the solution overview page.

AWS PrivateLink diagram for GitLab Dedicated

Documents


From Dedicated to Cells: A Technical Analysis
Introduction This document is intended to be a high-level summary describing how the existing GitLab Dedicated architecture could be used as a foundation for deployment and operating large numbers of GitLab Cell instances. Additionally, it explains certain decisions in the Dedicated architecture, and why these are beneficial to both GitLab Dedicated and GitLab Cells, and how they differ from other approaches, such as GitLab.com’s IaC, or GET. Note to readers: Please keep in mind that this is not a critique of GitLab.