bitnami helm chart to goharbor helm chart migration path

[frankcnxgpo]

Hi community,

Given Bitnami's recent deprecation announcement for their images and charts, we need to migrate from bitnami/harbor to the official goharbor/harbor Helm chart.

Current situation:

• Using bitnami/harbor chart in production
• Need to preserve all data (images, configurations, users)
• Looking for a proven migration path with minimal downtime

Key questions:

1. Has anyone done this migration successfully? What was your approach?

2. How to handle the data migration?

   • Database (PostgreSQL)
   • Registry storage (S3/filesystem)
   • Configurations

3. Any major gotchas between the two charts we should know about?

4. Is there a configuration mapping guide from Bitnami values.yaml to GoHarbor values.yaml?

Would appreciate any experiences or recommendations from those who've done this migration.

Thanks!

[MinerYang]

Hi @frankcnxgpo ,

Thanks for connecting with us. Even we can't provide a detailed migration plan, however there's a few quick hints

• for the PVC data, you need comparing the pvc name of the bitnami rendered and harbor-helm rendered. If theses two are different, you may need to modify the template of harbor-helm a little bit to make it consistent. And using the same storageclass to provision the PV (make sure the retain policy is retain, otherwise PV would be deleted once the bitnami harborhelm down.)
• if external redis or postgres or S3 storage is used, just configure the same credential for connecting.
• for other mandatory configurations like admin, harborAdminPassword, core.secret, core.tokenket, jobservice.secret, database.internal.password etc as same as before.

[frankcnxgpo]

thanks @MinerYang for the reply! appreciate the response.

from what I understand from your answer, it seems that both bitnami helm chart and the goharbor helm chart share the same database schema / pvc data "schema" / redis data "schema" and they can be inter-exchanged with each others as long. do I understand correctly? I was thinking there might be database/data schema differences between the two charts.