Drive adoption of the next-generation container registry by promoting the `Beta`
Context
In December 2023, we announced the beta
program for the next-generation container registry for self-managed customers. https://about.gitlab.com/blog/2023/12/04/gitlabs-next-generation-container-registry-is-now-available/
The new registry's benefit is improved reliability, performance, and support for online garbage collection. In addition, starting in 16.11, we are releasing some of the features that have only been available on GitLab.com. For example, accurate storage reporting, performance improvements for cleanup policies, and improved sorting and filtering with the API/UI.
Problem to solve
The problem is that it can be difficult for customers to discover the new registry. And some customers hesitate at the Beta tag. But, we can't go from Beta to GA without more customer feedback.
To address this, we've:
- Generated blog posts and shared with customers to socialize the updates
- Added a banner to the Admin page alerting them of the update.
- Added a banner to the docs
- Engaged with customers via TAMs
The goal of this issue is to expand our go-to-market strategy to include Support.
Proposal
Provide the Support team with easy-to-follow guidelines for why a customer should upgrade, what's involved, and what resources are needed.
What's needed from Support
If a customer has issues or questions with the container registry such as:
- How can I speed up garbage collection?
- Do you support online garbage collection?
- How much storage is being used? (available now)
- The cleanup policies are slow and do not delete everything (coming soon)
- How can I sign or attest images in my container registry? (coming soon)
- Sorting and filtering in the UI is very difficult (coming soon)
- Support for protected container images (coming later)
Point them to the beta
program for the next generation container registry.
- Feedback issue: Next generation container regis... (gitlab-org/gitlab#423459)
- https://docs.gitlab.com/ee/administration/packages/container_registry_metadata_database.html
What's needed from the customer
- Check out the docs: https://docs.gitlab.com/ee/administration/packages/container_registry_metadata_database.html
- If you have questions, add a comment to the feedback issue, gitlab-org/gitlab#423459 or reach out through a support ticket or issue.
What can the customer expect
- The time the migration takes will vary depending on the size of the registry. Customers with registries smaller than 100 TB can expect the migration to take less than a few hours. Customers with petabytes in their registry can expect the process to take a week.
- The proportion of downtime is a fraction of this total time. Check out this table for examples: gitlab-org/gitlab#423459
- The customer will need to bring their own database as this part of the work hasn't been completed yet. (We expect Distribution/Infrastructure to get to this in Q3/Q4)
Goals
The goal of the engagement is to increase the adoption of the registry so that we can confidently move to GA and help customers with some great new features and functionality.