Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Multi-Large Working Group

On this page


Property Value
Date Created June 22, 2020
End Date TBD
Slack #wg_multi-large (only accessible from within the company)
Google Doc Working Group Agenda (only accessible from within the company)
Issue Board TBD


The charter of this working group is to improve the operational efficiency of running multiple, large, independent GitLab sites without needing linear growth on staffing.

Scope and Definitions

In this context,

Examples of these types of instances would include, The working group may possible consider GitLab Federal, although this has to be an explicit decision, as operating federal entails clearances and such.

Sequence Order Of Deliverables

The following list outlines the order of deliverables per Multi-large (FKA Scaling) Working Group Agenda on 2020-07-13. The goal of this list is to define deliverables for the Working Group such that its charter can be finite.

Deprecate NFS
  1. Make Web/API work without NFS (issue tracker)
  2. Make CI/CD live traces work without NFS (issue tracker)
  3. Make Pages work without NFS (Scability:
Helm Charts
  1. Move Web/API nodes of .com to Helm charts (no issue tracker)
  2. Move Pages nodes of .com to Helm Charts (no issue tracker)
  1. Make Operator for Openshift (no issue tracker)
  2. Make Operator work with GKE (might be little work or no work) (no issue tracker)
  3. Use Operator for .com (no issue tracker)
Stateful Nodes
  1. Not sure when to move stateful nodes (Gitaly/PostgreSQL/etc.)? (no issue tracker)
Day 2 Automation
  1. Automate Day 2: scaling/backups/restores/upgrades (no issue tracker)

Use Case: Day 2 Operations

In this use case, we start with the 1K users Reference Architecture (Day 1) and map the necessary "moves" to grow and migrate said instance thorugh the available reference architecture milestones (Day 2: 2k, 3k, 5k, 10k, 25k, 50k) so that this can be managed within GitLab. Therefore, the working group focuses on the step-functions that scale the sites in code, which includes:

Horizontal Scaling Across Multiple Instances

For clarification, this working group is focused on horizontal scaling across multiple GitLab sites. Single-site scaling (e.g., is already covered under the charter of the Scalability Team.

Roles and Responsibilities

Working Group Role Person Title
Executive Stakeholder Steve Loyd VP of Infrastructure
Facilitator Gerardo "Gerir" Lopez-Fernandez (interim) Engineering Fellow, Infrastructure
DRI Gerardo "Gerir" Lopez-Fernandez Engineering Fellow, Infrastructure
Functional Lead Nailia Iskhakova Software Engineer in Test, Database
Functional Lead Andrew Thomas Principal Product Manager, Enablement
Functional Lead Gerardo "Gerir" Lopez-Fernandez Engineering Fellow, Infrastructure
Member Chun Du Director of Engineering, Enablement
Member Steven Wilson Manager, Distribution
Member Jason Plum Staff Engineer, Distribution
Member Tanya Pazitny Quality Engineering Manager, Enablement
Member Mek Stittri Director of Quality Engineering
Member Marin Jankovski Sr Engineering Manager, Infrastructure, Delivery & Scalability
Member Brent Newton Director, Infrastructure, Reliability Engineering
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license