Skip to content

Latest commit

 

History

History
92 lines (62 loc) · 4 KB

object_storage.md

File metadata and controls

92 lines (62 loc) · 4 KB
Raw
stage group info type
Systems
Geo
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
howto

Geo with Object storage (PREMIUM SELF)

Geo can be used in combination with Object Storage (AWS S3, or other compatible object storage).

Secondary sites can use one of the following:

  • The same storage bucket as the primary site.
  • A replicated storage bucket.
  • Local storage, if the primary uses local storage.

The storage method (local or object storage) for files is recorded in the database, and the database is replicated from the primary Geo site to the secondary Geo site.

When accessing an uploaded object, we get its storage method (local or object storage) from the database, so the secondary Geo site must match the storage method of the primary Geo site.

Therefore, if the primary Geo site uses object storage, the secondary Geo site must use it too.

To have:

See Object storage replication tests for comparisons between GitLab-managed replication and third-party replication.

Read more about using object storage with GitLab.

Enabling GitLab-managed object storage replication

The feature was made generally available in GitLab 15.1.

Secondary sites can replicate files stored on the primary site regardless of whether they are stored on the local file system or in object storage.

To enable GitLab replication:

  1. On the left sidebar, expand the top-most chevron ({chevron-down}).
  2. Select Admin Area.
  3. On the left sidebar, select Geo > Nodes.
  4. Select Edit on the secondary site.
  5. 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 site'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 site uses local storage.
  • A secondary site uses object storage.

Third-party replication services

When using Amazon S3, you can use Cross-Region Replication (CRR) to have automatic replication between the bucket used by the primary site and the bucket used by secondary sites.

If you are using Google Cloud Storage, consider using Multi-Regional Storage. Or you can use the Storage Transfer Service, although this only supports daily synchronization.

For manual synchronization, or scheduled by cron, see:

Verification of files in object storage

Files stored in object storage are not verified.