debian-mirror-gitlab/doc/administration/high_availability/object_storage.md
2020-04-08 18:37:08 +05:30

2.2 KiB

type
reference

Cloud Object Storage

GitLab supports utilizing a Cloud Object Storage service rather than NFS for holding numerous types of data. This is recommended in larger setups as object storage is typically much more performant, reliable, and scalable.

For configuring GitLab to use Object Storage refer to the following guides:

  1. Make sure the git user home directory is on local disk.
  2. Configure database lookup of SSH keys to eliminate the need for a shared authorized_keys file.
  3. Configure object storage for backups.
  4. Configure object storage for job artifacts including incremental logging.
  5. Configure object storage for LFS objects.
  6. Configure object storage for uploads.
  7. Configure object storage for merge request diffs.
  8. Configure object storage for container registry (optional feature).
  9. Configure object storage for Mattermost (optional feature).
  10. Configure object storage for packages (optional feature). (PREMIUM ONLY)
  11. Configure object storage for dependency proxy (optional feature). (ULTIMATE ONLY)
  12. Configure object storage for Pseudonymizer (optional feature). (ULTIMATE ONLY)

NOTE: Note: One current feature of GitLab that still requires a shared directory (NFS) is GitLab Pages. There is work in progress to eliminate the need for NFS to support GitLab Pages.