MarauderM
ZITADELβ€’2mo agoβ€’
18 replies
Marauder

FirstInstance vs DefaultInstance

βš™οΈConfiguration🏬Self-hosted❓Question❌Unsolved
FirstInstance vs DefaultInstance

Hello,

I am trying to figure out how to secure/harden my zitadel deployment in kubernetes. I am using helm charts.

I have been studying the configuration yaml file. And I ran into a confusion with
DefaultInstance
and
FirstInstance
.

Question 1: After deploying Zitadel to kubernetes via helm with default configurations, what am I logging into? FirstInstance or DefaultInstance?

Here's what I understood so far, please correct me if I'm wrong:

- Configuring
DefaultInstance
in the YAML file will not affect the FirstInstance - but it would affect the instances created after that.
- To configure the FirstInstance, I have to configure steps.yaml file.
-
PasswordComplexityPolicy
is in
DefaultInstance
configuration. Not
FirstInstance
.

Question 2: Does that mean I have to create a new instance so that I can have the
DefaultInstance.PasswordComplexityPolicy
?

Question 3: What's the recommended way to configure / maintain the instances? Because if the answer to question 2 is "yes", then it seems like I should ignore the
FirstInstance
and make a new instance and use only that.

I also saw this thread - https://discord.com/channels/927474939156643850/1116253718980075600/1116361734404440125. Sorry, but it didn't clear my confusion.
GitHub
ZITADEL - Identity infrastructure, simplified forΒ you. - zitadel/zitadel
zitadel/cmd/setup/steps.yaml at be9d2a53eb62bec2ba1f96439ab347dd2c1...
Was this page helpful?