Infrastructure Environments

1. You are here:
2. Engineering
3. Infrastructure
4. Infrastructure Environments

Maintained by:

On this page

• On this page
• Environments
  • Development
  • Demo
  • .org
  • Review Apps
  • Ops
  • Production
  • Staging
  • Pre
  • Release
  • GitLab Team Services
  • GitLap
  • Env-Projects
• Self-Managed
• Nodes

Environments

Terraform control for the environments can be found on ops

Development

Development happens on a local machine. Therefore there is no way to provide any SLA. Access is to the individual dev. This could be either EE/CE depending on what the developer is working on.

Demo

This should be a fully featured version of the current EE release. The high SLA and tightened access is to ensure it is always available for sales. There are no features (feature flags/canary/etc) that we do not ship.

.org

Currently there are two main uses for the .org environment:

• Builds.
• Repos that are needed in case GitLab.com is offline.

This is a critical piece of infrastructure that is always growing in size due to build artifacts. There are discussions to make a new build server where nightly CE/EE builds can be deployed or to move the infra repos to a new host that would be an separate (not gitlab.com) EE instance. Although the environment has dev in its domain name don't refer to it as dev since that could be confused with a local development environment.

Review Apps

Ephemeral app environments that are created dynamically every time you push a new branch up to GitLab, and they're automatically deleted when the branch is deleted. Single container with limited access.

Ops

The ops environment hold all infrastructure that is critical for managing GitLab.com infrastructure.

At this time it includes:

• Proxy for ElasticCloud.
• Internal monitoring infrastructure that serves dashboards.gitlab.net
• An isolated GitLab deployment that serves as a backup for all operations related GitLab repositories.
• CICD jobs for critical operations tasks such as backups and maintenance.
• Runners that need to connect to production infrastructure, such as GitLab chatops.

Production

Production will be full scale and size with the ability to have a canary deploy. Production has limited access. It consists of two stages:

• The canary stage is a subset of infrastructure that reaches a limited number of members of the community. We deploy to this stage first. For more information see canary testing.
• The main stage serves the remaining traffic for the wider GitLab community.

Staging

Staging has the same topology as Production and includes the same components, since they share the same terraform configuration.

Staging deployments precede production deployments as described in releases, but Staging is deployed a lot more frequently (at least every few hours, given the build is green). This would be a static environment with an pseudonymized production database. The DB is a snapshot of the production DB (updated only often enough to keep migration times to a minimum).

If you need an account to test QA issues assigned to you on Staging, you may already have an account as Production accounts are brought across to Staging. Otherwise, if you require an account to be created, create an issue in the access-request project and assign to your manager for review. Requests for access to database and server environments require the approval of your manager as well as that of one of the Infrastructure managers. The same access-request tracker should be used to request this type of access.

Pre

The pre environment is an environment used for validating release candidates used to prepare final self-managed releses and production patches. It does not have a full production HA topology or a copy of the production database.

Release

The release environment is an environment used for validating security releases, self-managed final monthly and patch versions. It does not have a full production HA topology or a copy of the production database.

GitLab Team Services

The GitLab Team Services Environment is a group of services for different sites run for GitLab.  It comprises the sites listed above.  These are not controlled in Terraform and seek to dogfood GitLab features such as AutoDevops or GitLab pages.

GitLap

The GitLap environment is an older domain primarily used for support testing. All DNS records under *.dev.gitlap.com and *.do.gitlap.com are controlled via terraform in the dev-resources repository.

The only important system is gitlab-runner-builder.gitlap.com which is used as a CI runner by the gitlab-runner project.

Env-Projects

This environment is used as a genesis project from which all other GCP projects used to support/manage/host gitlab.com are provisioned. No compute resources are present in the project, and it is used solely to provide a mechanism for centrally managing GCP projects, provisioning IAM roles/service accounts for infrastructure deployments within those projects, and controlling which APIs are enabled for each GCP project via Infrastructure as Code (terraform).

Reference: https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/-/tree/master/environments/env-projects

Self-Managed

These are environments that are run on-premises by the end-user. We have no influence, access or control of these environments.

Nodes

If you work at GitLab, also see the list of nodes managed by Chef to get an idea.