Skip to content

Deprecate pull-through cache feature

Context

The pull-through cache feature allows users to run the GitLab Container Registry as a pull-through cache to an upstream registry.

Problem

While this functionality is extremely useful, we have not made significant changes here, and our own blog mentions using the upstream version of the container registry to achieve this.

We don't have anything special to bring to the table for this functionality, and we can work upstream to introduce features and fix bugs that affect us (if ever). Removing this allows us to also remove the client code, which similarly exists upstream. Fundamentally, we can lose the maintenance burden of this code without sacrificing functionality.

This was one of the discussion points in #818 (closed).

Task

  • Add deprecation notice to docs and codebase to make it clear that this feature is deprecated and will be removed in %16.0. See !914 (diffs) for a similar example;
  • Mention deprecation in a release post (docs); - gitlab!108046 (merged)
  • Create and schedule an issue for the actual feature removal.

Deprecation 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. - gitlab!108046 (merged)
  • 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

15.8

Planned Removal Milestone

16.0

Edited by João Pereira