Unable to use helm chart with postgresql database about zitadel-charts HOT 5 CLOSED

@Be-El, @vavsab I created a user story in #91 that should address your issues. Please track and participate in #91.

from zitadel-charts.

Do I understand you correctly that you would like to have the secret data keys configurable for these secrets?

Other connection secrets like username, password, host etc are configurable in the ZITADEL yaml as described here. For secret ZITADEL config, you can use the secretConfig property in the Helm values.

from zitadel-charts.

Hi,

the helm chart requires certain secrets to be present. These are generated by cockroachdb. In a postgresql setup there is no cockroackdb, thus no secrets. This prevents the pods from starting since the secret cannot be mapped.

If I use empty fake secrets, the init container fails since it tries to copy //* to some destination. This fails if the secret is empty and no files are present.

from zitadel-charts.

An addition:

I can use fake secret content since the it is not used in the actual database setup in case of postgresql. Deployment fails nonetheless since the zitadel init code requires administrative access to the postgresql database. Since we have a shared postgreql cluster, we cannot use administrative credentials in third party applications. I've already created an issue in the zitadel core project, since code change will be required to solve this problem.

from zitadel-charts.

Do I understand you correctly that you would like to have the secret data keys configurable for these secrets?

Other connection secrets like username, password, host etc are configurable in the ZITADEL yaml as described here. For secret ZITADEL config, you can use the secretConfig property in the Helm values.

while we are here, I'm concerned that these secrets only set Cockroach env vars but do not set POSTGRES variables.

from zitadel-charts.