Skip to content

document internal postgres version upgrades #21865

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

Open
bdols opened this issue Apr 9, 2025 · 0 comments
Open

document internal postgres version upgrades #21865

bdols opened this issue Apr 9, 2025 · 0 comments
Labels
area/doc Issues to track documentation tasks

Comments

@bdols
Copy link

bdols commented Apr 9, 2025

I attempted an upgrade of a install that was frozen on chart 1.12.6 (harbor 2.8.6) to 1.16.2 (harbor 2.12.2) and it seems to me that this may not be supported because the database migration failed and the harbor instance's db was empty and initialized on postgres15. The harbor-db container in 2.12.2 doesn't contain postgres13 but does contain postgres 14 and postgres 15. I'm not sure how the database migration is supposed to work, but I don't see where this is documented.

If this is the case, I suggest that the helm upgrade documentation (https://goharbor.io/docs/2.12.0/administration/upgrade/helm-upgrade/) and/or the chart's README can have notes on postgres db requirements and/or intermediate upgrade needs.

Another possible solution could be to add a helm hook that prevents the upgrade if the previous chart version isn't greater than a specific version, but I'm not sure if that is fully implementable with helm.

@MinerYang MinerYang added the area/doc Issues to track documentation tasks label Apr 14, 2025
@MinerYang MinerYang transferred this issue from goharbor/harbor-helm Apr 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues to track documentation tasks
Projects
None yet
Development

No branches or pull requests

2 participants