## Context The Package team has been working on a new version of the Container Registry that relies on a [metadata database](https://docs.gitlab.com/ee/architecture/blueprints/container_registry_metadata_database/) to enable online garbage collection and unblock the implementation of several other features. With the new version now implemented, we've been working on the rollout, starting with GitLab.com (https://gitlab.com/groups/gitlab-org/-/epics/5523). We have defined a new [gradual deployment/migration plan](https://gitlab.com/gitlab-org/container-registry/-/issues/374) to support it, which has superseded the [previous one](https://gitlab.com/gitlab-org/container-registry/-/issues/191). ## Approach Due to having a new [migration plan](https://gitlab.com/gitlab-org/container-registry/-/issues/374), we'll need to investigate and implement additional changes required for delivering [Phase 1](https://gitlab.com/gitlab-org/container-registry/-/issues/374#phase-1-the-metadata-db-serves-new-repositories). This epic is meant to aggregate and track those tasks.