Add capacity 40 for container registry migration
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, 5, 10, and 25. We're currently running with a capacity of 25 in production.
What does this MR do and why?
Adds a new container_registry_migration_phase2_capacity_40 feature flag to enable a capacity of 40 concurrent migrations. This will enable us to achieve a higher migration throughput.
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_40)
=> true
[3] pry(main)> ContainerRegistry::Migration.capacity
=> 40MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.