Description taken from [gitlab-com/migration#36](https://gitlab.com/gitlab-com/migration/issues/36) Also see label [Object Storage](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Object%20Storage) The problem with shared file-systems is documented in [gitlab-com/migration#23](https://gitlab.com/gitlab-com/migration/issues/23). Currently, GitLab has multiple codepaths that rely on shared file-system access in order to work properly. Even the current implementation of object storage in GitLab EEP relies on a shared-file systems in order to work correctly. This issue is spread across multiple components of the GitLab application (ie, Platform, Discussion & CI) but, from our discussions, it seems like a solution could be rolled out in a fairly consistent manner, across the code-base.