Harbor Helm 1.8.1 HA with external backing services

[aceeric]

I'm using the 1.8.1 helm charts to stand up an HA Harbor registry on Kubernetes. To integrate with an external database it looks like the chart values.yaml wants an in-lined password. Is there any consideration being given to the idea of supporting templating for that so I can define the password with a Helm lookup function to get the password from a Secret provisioned by an external Postgres operator? Similarly, the S3 integration would benefit from the access key and secret key supporting this. (Potentially the Redis integration as well...) Thank you.

[xzizka]

Hello, we are trying to achieve nearly the same in our project. We are using ArgoCD fro deployment. The way we are trying now is to define the base of the deployment in one Git repo (same for all deployments) and in another repo linked with the ArgoCD we use kustomize to customize all necessary values, but maybe this is overcomplicated for your situation.

[siegenthalerroger]

+1 The s3 integration already allows this by loading from an existingSecret

[sylvainOL]

fyi, I've created https://github.com/goharbor/harbor-helm/pull/1244 in order to help on that. If it doesn't pass (because it's rather big), my plan was to start with database external first

[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.

[github-actions[bot]]

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.