Right now Workhorse supports the caching of repository archives on local filesystems: https://gitlab.com/gitlab-org/gitlab-workhorse/blob/b2949124ce5a792db3a1989b18cd4d220a58a50d/internal/git/archive.go#L72-81 I believe we disable this in Kubernetes to avoid a dependency on shared storage. However, with an upcoming feature to include LFS blobs inside of pointers inside the archive (https://gitlab.com/gitlab-org/gitlab/-/issues/15079), I wonder if we need to consider storing these archives in object storage via Workhorse. Note we already have a `Repository static objects` feature (https://docs.gitlab.com/ee/administration/static_objects_external_storage.html), but this relies on Cloudflare. I wonder if there is value in having Workhorse do this caching, especially if it has an S3 client already.