Replies: 2 comments 1 reply
-
@eliobischof or @stebenz can you have a look at this? |
Beta Was this translation helpful? Give feedback.
-
Oups, sorry for the late reaction. Do you mean the DB admin user that the Zitadel init job uses to connect to the DB or do you mean the first Zitadel user with role IAM_ADMIN that is created by the setup job? Either way, you need to configure them in the configmapConfig or the secretConfig. But I see an added value if the chart allows adding references to more configmaps and secrets that are then also passed to the zitadel binary via --config flag. Would that cover your use case? Would you mind creating an issue? |
Beta Was this translation helpful? Give feedback.
-
First off, the chart is well documented and the examples are really helpful.
I only have one question:
Sorry if I missed this in the chart, but is it possible to set the admin credentials using a Kubernetes secret? So I create the secret first and reference it in the
values.yaml
?Or are the admin credentials "hardcoded" and need to be changed after installation?
Thanks in advance!
Kind Regards,
Johannes
Beta Was this translation helpful? Give feedback.
All reactions