GitLab

GitLab
File:Gitlab-logo.svg.svg
Backup and Restore Cheat Sheet Failover Gitlab Runner Gitlab Runner/Cloud Runners Gitlab Runner/Plattform Evaluation Gitlab Runner/Security Evaluation Gitlab Runner/Shared Runners Gitlab Runner/Trusted Runners Monitoring Phabricator integration Replica Stewardship Test Instance Upgrade External resources: Production GitLab GitLab docs GitLab in MediaWiki GitLab in Phabricator

This page contains SRE related topics for GitLab. For GitLab application-specific information, user documentation, and policy, please see mw:GitLab on mediawiki.org.

GitLab is reachable at https://gitlab.wikimedia.org/. We run multiple instances of GitLab:

• gitlab1001 runs production GitLab serving https://gitlab.wikimedia.org/
• gitlab2001 runs a passive GitLab replica serving https://gitlab-replica.wikimedia.org/ (WIP)
• gitlab-ansible-test in WMCS gitlab-test project serving https://gitlab-test.wmcloud.org/

GitLab instances

gitlab1001 and gitlab2001 are setup using puppet. The configuration currently lives in profile::gitlab. Former configuration from gitlab-ansible was migrated completely to puppet (see T283076). GitLab is installed as a Omnibus installation on all instances. So all GitLab components are installed using the official packages and are executed on a single host. The reasons for this setup can be found in the Initialization docs in Mediawiki.

GitLab login is implemented with SSO using the CAS/SSO. So users will be redirected to idp.wikimedia.org to login to the SSO portal. Authentication is currently open to all users with a Wikimedia developer account.

GitLab runners

For our current and future runner setups, see GitLab/Gitlab Runner.

SSH fingerprints

See Help:SSH_Fingerprints/gitlab.wikimedia.org for an overview of all fingerprints at once.

Each gitlab server has 4 IPs on the same network interface. One IPv4 and one IPv6 for server, the standard sshd that admins use to connect to the individual backend (gitlab1001.wikimedia.org/gitlab2001.wikimedia.org) and one IPv4 and IPv6 for the service address (gitlab.wikimedia.org).

If you connect to the service as a user you _should_ expect to see the one for the service IP but currently you will see the one for the backend you are connecting to. Currently this is gitlab1001 but it could change when we switch data centers or fail over.

We are looking into getting a new configuration option into gitlab upstream to properly fix this. Meanwhile you can find fingerprints linked on the server pages, gitlab1001 and gitlab2001 and all fingerprints in a single place at Help:SSH_Fingerprints/gitlab.wikimedia.org.

also see the status of this ticket: phab:T296944

Tickets

• phab:T274459 (VM creation request)
• phab:T296944 (Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints)
• phab:T295481 (Setup GitLab Runner in trusted environment)