Update Design of the Container Registry Cleanup Policy for tags
Problem to solve
The Container Registry contains a multitude of image tags. For many users, there are a lot of stale tags inside the registry that have no value. We have created the Cleanup policy for tags feature to help remove the stale data to control storage costs related to the container registry.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Allison (Application Ops)
- Priyanka (Platform Engineer)
- Dana (Data Analyst) -->
User experience goal
Review the Cleanup policy UI and propose any possible design changes, including field names, text includes, etc to help refine the experience and better enable users.
Another important aspect of this work is to better align the form itself with Gitlab's Pajamas Guidelines around Forms.
Proposal
Create an updated design for the Cleanup Policies based on feedback.
| Current Iteration of the Design |
|---|
 |
Further details
Future iterations
- Near the "cleanup runs every x days" field, include a way for the user to select the start date (i.e. do it tomorrow, then every 7 days)
- Add the ability to run the cleanup policy manually (right now)
- Add a preview ability to get a list of image tags that would be removed if the policy was set to run as is
Permissions and Security
Documentation
The design changes should be purely superficial. The core functionality remains the same, but the documentation may need to be updated if field names change.
Availability & Testing
Tracking the end to end test in: gitlab-org/quality/testcases#1103