### Problem to solve In 13.11, we [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4368) the [consolidated object storage](https://docs.gitlab.com/ee/administration/object_storage.html#consolidated-object-storage-configuration), something that simplifies the configuration of object storage of all the services that [support](https://docs.gitlab.com/ee/administration/object_storage.html#storage-specific-configuration) it. The problem is that we still document the old way of configuring the object storage, which is specific to each service. This complicates things and makes the pages big and hard to scan. We do say that we recommend the consolidated form, so why also have the specific ones as well? ### Proposal Remove mentions of non-consolidated object storage for services that support it. From the table in https://docs.gitlab.com/ee/administration/object_storage.html#storage-specific-configuration, the services that **don't** support the consolidated form are: - Backups - Container Registry - Mattermost (they have their own [config](https://docs.mattermost.com/configure/file-storage-configuration-settings.html)) - Runner caching - CI secure files For the rest, clean up the docs and remove the specific storage information: - [ ] Job artifacts including archived job logs https://gitlab.com/gitlab-org/gitlab/-/merge_requests/108360 - [ ] LFS objects - [ ] Uploads - [ ] Container Registry - [ ] Merge request diffs - [x] Packages https://gitlab.com/gitlab-org/gitlab/-/merge_requests/106421 - [ ] Dependency Proxy - [ ] Terraform state files - [ ] Pages content