Can't find tag retention based on labels, despite screenshots showing this feature

[MichaelKueller]

We want to setup tag retention policies based on labels, which we set as part of our deployment pipleline. That way we can identify which images have been deployed to production and make sure not to delete the last n versions that have been deployed to production. This is in contrast to keeping the last n images pushed to harbor, as none of the last n images might have been pushed to production.

In the screenshot below (found in https://github.com/goharbor/harbor/issues/8695) I saw that such a feature exists, but in my harbor installation (v. 1.9.4) the field to define labels is missing. Has this feature been removed, or where can I find it?

[xaleeks]

@MichaelKueller Labels as a filter condition was removed shortly after it was released, it was causing some issues because of how they are created at system and project level but then interacted with the repository matching conditions, giving us some nasty side effects. We will eventually add labels back when we have bandwidth for testing. I've added this as a requirement to the backlog.

I'm curious if labels are enough for tracking image deployed in the wild like you described. ie how do you enforce that they are added when they are deployed and removed when they are taken down.

[MichaelKueller]

Thank you for your response. In our case our deployment tool adds the labels during the deployment process. In harbor we would then set up a rule to retain the newest 5 images that are labelled with "deployed-to-production". So there is no need to remove the labels. If labels are not available for retention policies, how would you suggest to keep the last 5 images that have been deployed to production, additionally to the newest 5 images?

[claflico]

i would like to be able to delete by labels as well please.

[Andreiaotto]

We also have this use case, we want to migrate from quay.io to harbor, as we have commitID as tag, we don't know what's the tag name to add rules. With labels we can define the label in our pipelines and define retention rules.

Is there any recommendation while there is no such feature available?

thank you!

[kitenco]

we need labels for retention rules too, same use case (deployment to production)

[fabricev]

Agreed with everbody above, retentions policies based on labels would be really nice.

[anatoly-kryzhanovsky]

+1

[romanglogowski-millennium]

+1

[MichaelKueller]

Hi @xaleeks are you able to give an update about this feature? Is it going to return in one of the next releases? The lack of it is starting to cause quite some extra manual work and looking at the comments above it seems we are not the only ones who need it.

[kitenco]

Hi @xaleeks are you able to give an update about this feature?

[github-actions[bot]]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[MichaelKueller]

Are there any updates? Will this feature ever come back?

[Yingrjimsch]

Is this planned? We would like to use that too.

[Kajot-dev]

This feature would be nice. For example we would have a service which scans kubernetes/OKD cluster for images which are in use and labels them so, they won't get deleted by retention policies and this way the service would be independent from tags (and reduced risk from overlapping the tag names with users/CI/CD

[akramadel]

Is there a plan to release this feature soon?