This is a meta issue tracking the implementation of Tag Retention Policies
Not many people have the luxury of unlimited storage. For images and tags that are effectively ephemeral (like those built and tagged for use only by an intermediate process in a CI pipeline) it does not make sense to keep these tags around for an extended period of time, consuming precious resources. Other tags, like those correlating to released or deployed software may need to be kept for an extended period of time or even forever for various legal or compliance reasons. While this is possible today via Harbor's API, Harbor Administrators could greatly benefit from having this functionality built-in to harbor itself.
As this is a large feature and I can really only work on it in my free time, I'm splitting it up into multiple smaller issues. If you see something you're interested in working on feel free to contribute!
I envision this being implemented in roughly this order:
- Groundwork
- Common types / interfaces / boilerplate
- Filter chain builder
- Filter Implementations
- Keep Everything
- Delete Everything
- Always Keep tag
x - Always Delete tag
x - Keep if downloaded at least
ndays ago - Keep most recent
ntags - Delete tags older than
ndays
- API
- CRUD for policies
- Get logs for execution
- Trigger tag processing
- Misc
- Run tag processing on a schedule
- UI Proposal drafted
The UI proposal draft can start at any stage. The actual scheduling / execution of tag processing will be disabled until the feature is fully implemented. This way we can work on this in small, reviewable chunks.