Deploying self-managed GitLab on AWS
GitLab on AWS from a single EC2 instance built from GitLab's community AMIs to a reference architecture with RDS PostgreSQL, managed Redis and S3 object storage.
GitLab deployment and infrastructure
Where and how self-managed GitLab runs: install methods, cloud providers, managed databases, object storage and hardware requirements.
Deploying self-managed GitLab on Microsoft Azure
GitLab on Azure from the Marketplace image to a production layout with Azure Database for PostgreSQL Flexible Server, extension allow-listing and Azure Blob object storage.
Deploying self-managed GitLab on Google Cloud
GitLab on Google Cloud from a single VM to a reference architecture with Cloud SQL, a managed Redis service and Google Cloud Storage buckets per object type.
Running GitLab on Amazon RDS, Cloud SQL or Azure Database for PostgreSQL
Using a managed PostgreSQL service for GitLab: the admin roles each provider needs, required extensions, version limits per GitLab release and pg_dump compatibility for backups.
Configuring GitLab object storage on S3, GCS, Azure or Ceph
Setting up the consolidated object storage form, which providers GitLab tests versus community-documented ones like Ceph RGW, and the data types that still need separate settings.
Running GitLab in Docker for production
When the GitLab Docker image is a sound production choice, volume layout and upgrades, and the support trade-off GitLab notes for Docker and Compose deployments.
GitLab on OpenShift with the GitLab Operator
Installing GitLab on OpenShift through the Operator instead of the raw Helm chart: security context constraints, external stateful services and Operator-driven upgrades.
FIPS-compliant self-managed GitLab
Running GitLab in FIPS mode for federal and regulated customers: FIPS container images, PBKDF2-SHA512 passwords, SSH key length rules and known issues on FIPS hosts.
GitLab server requirements: CPU, memory, storage and databases
The hardware and software baseline for self-managed GitLab: vCPU and memory, Gitaly storage, PostgreSQL and Redis versions by GitLab release, and why burstable instances and NFS are discouraged.
Moving self-managed GitLab off NFS
Planning the move from NFS-backed GitLab to object storage and local SSD Gitaly storage: what data moves where, and the incremental job log and artifact settings multi-node setups need.
