Error when installing with FirstInstance
#306
-
Hi! # values.yaml
replicaCount: 1
zitadel:
masterkeySecretName: "zitadel-masterkey"
configSecretName: zitadel-config
configSecretKey: config.yaml # config.yaml coming from the opaque secret `zitadel-config`
ExternalSecure: true
ExternalDomain: zitadel.vindelicorum.eu
TLS:
Enabled: false
FirstInstance:
Org:
Name: ZITADEL
Human:
UserName: zitadel-admin
Password: "Zvpj9rdjKuy35syuAOmGtuvNa76MyPKPJAjZ5i4jaHcvUtCy1kYpaxynHTDI6NlgCkR4DarFbpNEYlXFnN0rpk46kwDvxScunvJM"
Database:
Postgres:
Host: zitadel-postgres-rw
Port: 5432
Database: zitadel
MaxOpenConns: 20
MaxIdleConns: 10
MaxConnLifetime: 30m
MaxConnIdleTime: 5m
User:
Username: zitadel
Password: "8GJHD4M3EgKUFPdOqmYY3XIpJ4DwCApn7H6DVrnqvAIgrk7rEtBg4bQrDAD56CdAArHSCzDvQFtK3BQE3pgwXTkrq2Gr5rCU5Oy8"
SSL:
Mode: disable
Admin:
Username: postgres
Password: "4XFJWrT06QYA0IshErSvvN5tSByWcI5BQcAhx12d2BU5Xcyvw2AzqHYKBfMVonoOxRYuwGZouYxDHDCNclJRFQowpGViYKuJJkp2"
SSL:
Mode: disable Without the
Init then succeeds but the server logs:
For docker-compose it can be mounted as extra file but I don't see how this would be done with the chart. Is there something missing in the docs here? ChartVersion: 8.11.2 Without the Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hm I think you need to pass the first instance settings as a steps and not as the config. |
Beta Was this translation helpful? Give feedback.
-
It shows here that it is possible in the configmapConfig in the values file, but I don't want to have a password in there (The values file is commited to git), but provide it (and the whole config with all passwords) as a secret. Can a secret be passed to the steps? |
Beta Was this translation helpful? Give feedback.
-
The problem was that the password was too long and did not contain any special characters. When only missing special characters at least the error message makes sense, when it is too long it just fails with this strange database migration failure. |
Beta Was this translation helpful? Give feedback.
The problem was that the password was too long and did not contain any special characters. When only missing special characters at least the error message makes sense, when it is too long it just fails with this strange database migration failure.