Container Registry garbage collection on a secondary node
This issue should be converted into an epic after some research. This includes at least documenting the garbage collection for a secondary node but I think it's possible that we will need to create some tools to make that convenient.
Context
The GC ran on the primary doesn't have any impact on the sync process on secondary. When images are removed, the blobs are kept in storage forever until the GC process picks them up. So secondary has to have its own GC process. We have documentation on the GC process for Registry https://docs.gitlab.com/ee/administration/packages/container_registry.html#container-registry-garbage-collection
Edited by Valery Sizov