Skip to content

Deprecation: Container Registry Object Storage Metadata Support

Deprecation Summary

We are deprecating the legacy Container Registry that uses object storage for metadata in favor of the Container Registry Metadata Database. This deprecation affects self-managed GitLab instances that are currently using the object storage-based metadata approach.

Impact to end users: Self-managed customers currently using the legacy Container Registry with object storage metadata will need to migrate to the Container Registry Metadata Database to continue receiving feature updates and support. The legacy method will enter maintenance mode and will not receive new features or improvements.

Documentation

Product Usage

The deprecation of the legacy Container Registry object storage metadata is necessary to:

  • Reduce the engineering maintenance overhead of supporting two different metadata approaches
  • Improve Container Registry performance and reliability
  • Enable new Container Registry features that require database metadata
  • Align self-managed instances with the architecture already used on GitLab.com

User Action Required: Users should migrate from the legacy object storage metadata approach to the Container Registry Metadata Database using the migration guidelines linked above.

Breaking Change?

Does this deprecation contain a breaking change? No

This deprecation does not immediately introduce a breaking change. The legacy method will remain supported in maintenance mode for existing customers, with clear communications that they should migrate at their earliest convenience.

Affected Customers

Who is affected by this deprecation:

  • Self-managed users
  • GitLab.com users (already using metadata database)
  • Dedicated users

What pricing tiers are impacted:

  • GitLab Free
  • GitLab Premium
  • GitLab Ultimate

Deprecation Milestone

This deprecation will be announced in milestone: 19.0

Planned Removal Milestone

The feature/functionality removal milestone: To be determined

Note: The legacy method will remain supported in maintenance mode. A future removal milestone will be determined based on adoption rates and customer feedback, potentially in 20.0 or 21.0.

Links

Timeline

  • Deprecation announced in 19.0
  • Documentation updated to mark legacy method as deprecated
  • Support team prepared with guidance for customer inquiries
  • Migration tooling validated and documented

Communication Plan

DRI Product Manager: @trizzi

Internal Communication Plan

  • Support Preparedness issue created
  • Guidance for Engineering, Product, Security, Customer Success, and Sales created
  • Internal Slack announcement posted
  • Cross-functional teams notified of timeline and customer impact

External Communication Plan

  • Customer announcement plan developed (timeline, audience, channels)
  • Legal and corp comms approval obtained for customer communications
  • Release post content prepared
  • Documentation team notified for updates

Labels

References

Edited by 🤖 GitLab Bot 🤖