Jakub Jaruszewski

So essentialy if you have **multiple secret stores** (and thus multiple backends available) installed or just have the **kwallet >= 5.97**, (beacuse it supports secretservice+libsecret as well - see https://invent.kde.org/frameworks/kwallet/-/merge_requests/11)...

That would be great to have! We're adding these besides the helm chart currently

Does you ArgoCD use `helm template` or `helm upgrade/install`?

@EsDmitrii I'm asking, because there are certain secret values that depend on a `lookup` function. If it's not available and values are not provided directly it will generate a new...

It's not managed by harbor but by the helm and in your case the ArgoCD and its ServiceAccount. Since you don't use `helm install` but a custom templating, not all...

Harbor does not modify secrets, but the template is configured to generate the new secret values if current ones are not available for it (it does not access them because...

> I understand that ArgoCD trying to sync Harbor with actual state in Git, but how Harbor modify secrets and deployments in k8s without granted permissions to it? Argo trigger...

@EsDmitrii Just provide the secret values to the chart config so they are not generated each time or use `existingSecret` (but the chart does not provide `existingSecret` option for all...

The issue is that `lookup` function will - Return the object during install/upgrade - Return **empty object** if object does not exist OR either `helm template` or `--dry-run` option is...

Couple things: - If you use helm template, `lookup` does not work - as of now chart does not create any secrets by itself for redis internal or external -...