Announcing an exciting update to the GitLab.com Container Registry

Oct 25, 2021 · 2 min read
Tim Rizzi GitLab profile

In the coming weeks, we are planning to roll out a new version of the Container Registry on GitLab.com. Prior to deploying this major update, we wanted to clearly communicate the planned changes, what to expect, and why we are excited about this update.

If you have any questions or concerns, please don’t hesitate to comment in the epic.

Context

In milestone 8.8, GitLab launched the MVC of the Container Registry. This feature integrated the Docker Distribution registry into GitLab so that any GitLab user could have a space to publish and share container images.

But there was an inherent limitation with Docker Distribution as all metadata associated with a given image/tag was stored in the storage backend. This made using that metadata to build API features like storage usage visibility and sorting and filtering unfeasible. With the most recent update to the Container Registry, we’ve added a new metadata database that will store all of the metadata in Postgres instead of the storage backend. This will allow us to unblock many of the features that you’ve been asking for.

Why we are excited

The plan

We're planning a phased migration, starting with newly-created repositories. We'll roll this out incrementally to maintain safety for those customers and provide our team with an opportunity to identify and address any concerns.

Timing

We're starting the percentage-based rollout on October 26th, 2021, with GitLab internal projects' customers with less usage, which we expect to take 4 to 6 weeks. For more information about the planned, percentage-based rollout, please refer to this epic.

Once we complete that work, we’ll switch to customers who heavily use the Container Registry for new repositories.

FAQ

“Learn more about @gitlab's Container Registry update” – Tim Rizzi

Click to tweet

Open in Web IDE View source