GitLab Geo with Object storage
GitLab Geo can be used in combination with Object Storage (AWS S3, or other compatible object storage).
At this time it is required that if object storage is enabled on the primary, it must also be enabled on the secondary.
The secondary nodes can use the same storage bucket as the primary, or they can use a replicated storage bucket. At this time GitLab does not take care of content replication in object storage.
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
Complete these steps on all nodes, primary and secondary.
When using Amazon S3, you can use CRR to have automatic replication between the bucket used by the primary and the bucket used by the secondary.
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, please have a look at: