How does the Zitadel Helm setup work in regards to system user keys?
Original message was deleted
Rdon't you provide the system key yourself?
R(I'm clearly out of my depth here). Hoping for someone else to chime in 
Fhm in docker compose we write it to disk...
@Elio does the chart allow it to be written to a secret?
@Elio does the chart allow it to be written to a secret?
Rhttps://github.com/zitadel/zitadel-charts/tree/main/examples/6-machine-user shows how to do it - and the STDOUT from running the zitadel install shows you a snippet to export the secret.
https://raw.githubusercontent.com/zitadel/zitadel-charts/main/examples/6-machine-user/zitadel-values.yaml gives a working config
https://raw.githubusercontent.com/zitadel/zitadel-charts/main/examples/6-machine-user/zitadel-values.yaml gives a working config
GitHub
This repository contains Helm charts for running ZITADEL in Kubernetes - zitadel/zitadel-charts
EThe key and the secret are only created once on the initial setup, yes. But k8s should retry mounting the secret to the other apps deoloyment until it exists, doesn't it? Else, you probably have to orchestrate the other apps deployment to be created not earlier than when the setup job succeeded?
Dit I get your question right?
Dit I get your question right?