Skip to content

Add capacity 5 for container registry migration

João Pereira requested to merge capacity-5 into master

Context

We're working on the migration of old container repositories to the new platform on GitLab.com (&7423 (closed)). This process is driven by Rails, as explained in &7316 (comment 897867569).

As part of the Rails driving logic, we have the ability to control how many repository migrations can happen "at the same time". This is controlled by the container_registry_migration_phase2_capacity_N feature flags, where N is the maximum number of migrations. Currently N can be one of 1, 2, 10, and 25. We're currently running with a capacity of 2 in production.

What does this MR do and why?

Adds a new container_registry_migration_phase2_capacity_5 feature flag to enable a capacity of 5 concurrent migrations. This will an intermediate step to ease the transition between 2 (current) and 10 (next) capacities.

The rollout issue for all migration feature flags is #350543.

Screenshots or screen recordings

NA

How to set up and validate locally

[1] pry(main)> ContainerRegistry::Migration.capacity
=> 0 # default
[2] pry(main)> Feature.enable(:container_registry_migration_phase2_capacity_5)
=> true
[3] pry(main)> ContainerRegistry::Migration.capacity
=> 5

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports