Leverage Docker tag expiration policies at repository level
Problem to solve
Users are building many Docker images as part of their pipelines. Many of these images are only needed for a short time. There isn't a good way for developers to delete these images, so they frequently don't. This results in either ballooning storage costs, or the Admin trying to remove images manually via the Container Registry API, which is error prone and inefficient.
- I as a systems administrator, need to ensure that my development teams are expiring unused images, so that I can run garbage collection, delete them from storage and lower the cost of storage.
- I as a developer, need the ability to check my project's and Docker repositories' expiration policy, so that I can ensure that my important images (ones required for a given release) are not accidentally removed.
Add a new element to the project's Container Registry that exposes the project's expiration policy and allow developers (and above) to disable or adjust the rule at the repository level.
- Developers (and above) can disable or update the expiration policy at the repository level
User Interface (These designs are still in motion and are subject to change)
Related to #15398
Original comment: #15398 (comment 249247990)