Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update all retention policies of all project #20978

Closed
wy65701436 opened this issue Sep 30, 2024 Discussed in #20972 · 3 comments
Closed

Update all retention policies of all project #20978

wy65701436 opened this issue Sep 30, 2024 Discussed in #20972 · 3 comments

Comments

@wy65701436
Copy link
Contributor

Discussed in #20972

Originally posted by s4ndalHat September 27, 2024
Hello everyone,

Recently, we migrated our harbor instances across different cluster, and after migration, all scheduled retention policies stopped wotking..

I've looked at some issue on the repo, and the workaround is to force update the schedule of retention policies from the Harbor UI.
However, having almost 100 projects, it's plenty of manual operations to do, so I'm asking if there is an easy way to do it.

Harbor version: 2.0.2 installed by helm chart
Kubernetes version: 1.26.3

Thank you

@wy65701436
Copy link
Contributor Author

Hi @s4ndalHat,

I've converted this into an issue. Could you please provide more details?

  • Did you migrate your Harbor instance from an older version to v2.0.2? If so, what was the previous version?
  • When you mention that the policies stopped working, were they changed to a "disabled" status? And by "force update," do you mean re-enabling the policies?

I also suggest creating a sample automation script to manage this by calling the Harbor API. Additionally, please note that Harbor v2.0 is no longer supported. I recommend upgrading to the latest version or at least v2.10+.

@s4ndalHat
Copy link

Hi @wy65701436 ,

  • I migrate the harbor instance from two different clusters, but with the same version.
  • The scheduled policies didn't work anymore, and they weren't disabled at the UI but still scheduled as daily cron.

By force update, i mean change the configured schedule "Daily" to "Weekly" then configured back to "Daily".

An update will be planned on this particular instance, but at the moment we would want to solve it first...

@s4ndalHat
Copy link

I will close this issue,
After changing the configuration manually, its solved. And we also planned to run an upgrade of the instance shortly.

Thanks for the instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants