## Context This is part of the work to upgrade and migrate the GitLab.com container registry to a new version backed by a metadata database and online garbage collection (https://gitlab.com/groups/gitlab-org/-/epics/5523). This will be achieved following the gradual migration plan detailed in https://gitlab.com/gitlab-org/container-registry/-/issues/374. This specific epic is meant to collect the tasks required for the gradual rollout of [Phase 1](https://gitlab.com/gitlab-org/container-registry/-/issues/374#phase-1-the-metadata-db-serves-new-repositories) described in the migration plan. This will be achieved by manipulating a set of feature flags from the Rails side. We'll split the work into three portions, in this order: 1. **GitLab Org**: We'll start by testing with some custom-made container repositories under `gitlab-org/` and then allow all of its new container repositories to be handled by the metadata DB: https://gitlab.com/gitlab-org/gitlab/-/issues/336873; 1. **General**: Following the GitLab Org rollout, we will proceed with a general percentage-based roll out for everyone, excluding major customers (see next); 1. **Major customers**: To reduce the risk of impacting users of the GitLab.com container registry that have large amounts of data, a very high activity, or very high availability/stability requirements, we will exclude these from (2) and handle them in this step with a manual gradual rollout, customer by customer. ## Cross-Group Dependencies - [x] Production database cluster: https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/324 ## Status https://gitlab.com/gitlab-org/gitlab/-/issues/336875 was completed today and as such Phase 1 is now complete. Keeping this epic open until we clean up the related feature flags.