UX: Show when registry usage is estimated
Context
Per &9413, we should let customers know when their registry usage is so large that we are displaying an estimate of their storage usage rather than the precise calculation.
Approximately ~80 namespaces affected
Designs
TBD
Additional notes
- From this discussion -- https://gitlab.com/internal-handbook/internal-handbook.gitlab.io/-/merge_requests/2820#note_1397670465 -- "what do you think about changing the name "estimated" to "delayed/queued calculation" or something like that. Estimated makes it sounds worse than it is, as the number is accurate after GC runs."
- I think "delayed" is OK, as long as we're clear about what it means. To recap:
- For the precise measurement we sum the unique layers of tagged images (those visible in the GitLab UI/API). This means that as soon as the user deletes some tags, the displayed value will be updated to reflect that, even before online GC kicks in to actually delete the image layers that were left untagged (if any), which happens 24h ahead in time.
- For the "delayed" measurement, we sum the unique layers of all images, tagged or not. As a consequence, when users delete a bunch of tags, the displayed value won't reflect any change. That change will only be reflected after online GC kicks in and actually deletes the image layers that were left untagged (if any), which happens 24h ahead in time.
Edited by Alex Martin