Problem Validation: Container Registry Garbage Collection
What's this issue all about? (Background and context)
We should conduct a survey to better understand users' usage patterns and satisfaction in regard to the Container Registry garbage collection.
What are the overarching goals for the research?
Solidify GitLab’s understanding of how Self-Managed instances manage their storage usage of the registry.
What research questions are you trying to answer?
- What types of storage Gitlab’s Self-Managed customers are using?
- How often and with what settings garbage collection is being run?
- What is an acceptable downtime/read-only window?
What persona, persona segment, or customer type experiences the problem most acutely?
Sidney (Systems Administrator)
- Since the migration to v3 of the Container Registry will be a big change, we should survey all GitLab self-managed instance-level Administrators.
- We can extend this to non-GitLab users, but the former will be most important.
What business decisions will be made based on this information?
The collected results will allow us to prepare a migration plan and tooling for self-managed registries in the context &2313 (closed), which will be required for users to adopt the upcoming registry database.
What, if any, relevant prior research already exists?
- We recently add
container_registry_vendor
to the usage ping, which will help us to understand the ratio of Self-Managed instances using the GitLab Container Registry or an external one within their instance. - We have a live survey in #1064 (closed) that a common question about storage providers.
What timescales do you have in mind for the research?
Ideally, we'd have an answer within the next 4 weeks.
Who will be leading the research?
Relevant links (opportunity canvas, discussion guide, notes, etc.)
- Problem validation issue
- Discussion guide
- Qualtrics survey (not created yet)