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

Upgrade harbor to v2.8.2 #1664

Closed
2 of 7 tasks
raviranjanelastisys opened this issue Jul 5, 2023 · 1 comment
Closed
2 of 7 tasks

Upgrade harbor to v2.8.2 #1664

raviranjanelastisys opened this issue Jul 5, 2023 · 1 comment
Labels
kind/improvement Improvement of existing features, e.g. code cleanup or optimizations.

Comments

@raviranjanelastisys
Copy link
Contributor

What Chart should be upgraded?

Upgrade harbor to v2.8.2 - https://github.com/goharbor/harbor/releases/tag/v2.8.2
Some changes are made related to tag retention policy , which we have started recommending to use - goharbor/harbor#18708

goharbor/harbor@v2.8.1...v2.8.2

Why should this Chart be upgraded?

  • We need to perform a security upgrade.
  • We need it for a new feature: which feature (link to blocked issue).
  • We need to keep up to prevent future issues.
  • Other: Write the reason here

lots of enhancements, new features, and bug fixes
Acceptance criteria

  • I checked the migration of the new Chart:
    • I upgraded a Chart and determined that no migration steps are needed.
    • I upgraded a Chart and added migration steps.
  • I tested the functionality provided by the new Chart (e.g., Auth flow, Grafana dashboards, etc.)
@raviranjanelastisys raviranjanelastisys added the kind/improvement Improvement of existing features, e.g. code cleanup or optimizations. label Jul 5, 2023
@raviranjanelastisys
Copy link
Contributor Author

Closing, as our chart upgraded to latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/improvement Improvement of existing features, e.g. code cleanup or optimizations.
Projects
None yet
Development

No branches or pull requests

1 participant