Removal: Support for external container registries in GitLab

Removal Summary

GitLab supports, using an external container registry with GitLab as an auth endpoint.

We've been able to support that because, until recently, GitLab's fork of Docker Distribution was compatible with the upstream version. However, that is no longer the case.

In recent months, GitLab has updated the GitLab Container Registry with scalability, performance, and UX improvements that are no longer compatible with the upstream Docker Distribution.

So, we are announcing the deprecation of this feature and will plan the associate removal, #376217 (closed), for GitLab 16.0.

Required changes

Update the docs to make it very clear that we no longer provide support for third-party registry compatibility. Use an external container registry with GitLab as an auth endpoint is the most prominent section.

Breaking Change Tasks

Affected Topology

This affects Self-Managed users of GitLab.

Affected Tier

All tiers are affected.

  • Free
  • Premium
  • Ultimate

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager: @heather.
    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @cfoster3
  • Your GPM @jreporter has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

Planned Removal Milestone

Links

Edited by João Pereira