As a part of the effort in creating retention and expiration policies for the docker container registry we need to create dedicated documentation and link to it in the user interface,
We would probably need to extend the following part of the documentation:
@trizzi@icamacho@axil With @sabrams we had a conversation around the expiration algorithm and @sabrams wrote down a very nice list of how the process work. We were thinking that maybe adding it to the docs:
The expiration policy logic starts by collecting all of the tags for a given repository, then goes through a process of removing tags from the list until only the ones to be deleted remain:
it gets all of the tags for a given repository
it removes the latest
it runs the name regex, removing non-matching names
it removes any that do not have a manifest (not part of the options)
As we discussed, I'm all for adding some form of this to the docs. If we were confused as to which settings took priority over others, I'm sure some users will be too.
@trizzi I am not sure about the scope of this issue: does it encompass the documentation for the whole feature or only for API + Setting page?
If it encompasses the whole feature ( settings page + widget on the container registry #37242 ) what do you think if we practice the iteration value by creating the docs before or while we are working on the feature itself? We can easily mark: this feature is going to be available from 12.9 to avoid confusing the users.
@nmezzopera I think we should get out the project-level settings page docs as soon as we can to give users visibility to the feature and start providing feedback. We can add the repository-level specifics (on the repository list page) as a 2nd iteration.