Geo with Object storage (PREMIUM ONLY)
Geo can be used in combination with Object Storage (AWS S3, or other compatible object storage).
Currently, secondary nodes can use either:
- The same storage bucket as the primary node.
- A replicated storage bucket.
- GitLab manage replication, follow Enabling GitLab replication.
- Third-party services manage replication, follow Third-party replication services.
Enabling GitLab managed object storage replication
Introduced in GitLab 12.4.
WARNING: This is a beta feature and is not ready yet for production use at any scale. The main limitations are a lack of testing at scale and no verification of any replicated data.
Secondary nodes can replicate files stored on the primary node regardless of whether they are stored on the local filesystem or in object storage.
To enable GitLab replication, you must:
- Go to Admin Area > Geo.
- Press Edit on the secondary node.
- In the Synchronization Settings section, find the Allow this secondary node to replicate content on Object Storage checkbox to enable it.
For LFS, follow the documentation to set up LFS object storage.
For CI job artifacts, there is similar documentation to configure jobs artifact object storage
For user uploads, there is similar documentation to configure upload object storage
If you want to migrate the primary node's files to object storage, you can configure the secondary in a few ways:
- Use the exact same object storage.
- Use a separate object store but leverage your object storage solution's built-in replication.
- Use a separate object store and enable the Allow this secondary node to replicate content on Object Storage setting.
GitLab does not currently support the case where both:
- The primary node uses local storage.
- A secondary node uses object storage.
Third-party replication services
When using Amazon S3, you can use CRR to have automatic replication between the bucket used by the primary node and the bucket used by secondary nodes.
For manual synchronization, or scheduled by