Update the design of the container registry error state
Problem to solve
During a recent outage: gitlab-com/gl-infra/production#2381 (closed) it was brought up that in various places in the GitLab UI, we will show incorrect information. If the API calls to GitLab fail, we do not indicate a problem with the Container Registry, but instead return nil values. This is a serious problem as scripts may rely on the ability to find tags to determine if an object needs to be built.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Simone (Software Engineer in Test)
User experience goal
- We communicate that the registry is unavailable
Proposal
Update the design of the Container Registry error state to ensure users are aware when the registry is down.