set most recently pushed retention policy to replicated harbor #23524
Unanswered
ArcticFoox
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When I apply a “retain the most recently pushed artifacts” retention policy in a replicated Harbor environment, the replication order seems to cause an issue.
Because the newest artifacts are pushed first during replication, the retention policy ends up keeping the oldest artifacts instead of the actual most recent ones after replication is completed.
Is there any recommended way to handle or avoid this behavior?
All reactions