Login V2 in a multi instance environment with Helm
I'm trying to test Login V2 with 4.0.1 on a Helm/Kubernetes environment but I wonder how it is supposed to work. It seems the zitadel-login image needs a PAT of a explicit instance and a appropriate Host overwrite to start. If you only need a single tenant, this happens automatically (FirstInstance configuration) but otherwise you need to do it manually. It doesn't seem feasible to start a container per Zitadel Instance, but I couldn't find a way to start Login V2 tenant independent with a system key.
In addition (but this could be due to misconfiguration?) it doesn't seem to use any existing setting in the instance. I have no external login enabled and disabled every language except English and German but it shows many more and crashes when choosing one of the disabled. Additionally the sentence "or sign in with" is shown, without anything to choose from. Last but not least it ignores any existing translation, so this alone would force us to customize it for every instance just for a few words.
Am I missing something or do I just need to wait a little more until it stabilizes?
OT: The new ui will be a real improvement and the Zitadel works nicely for our use cases until now 👏
2 Replies
"or sign in with" is already solved:
https://github.com/zitadel/zitadel/pull/10402
GitHub
fix(loginV2): hide sign-in-with-idp if none are configured by jonas...
Which Problems Are Solved
Don't show the external IdP section, if none are configured.
How the Problems Are Solved
Checks if the length of identityProviders is non-empty.
Additional Chang...
I answered the question about the multi instance setup here
GitHub
Multi instance setup with LoginV2 · Issue #379 · zitadel/zitadel-...
Preflight Checklist I could not find a solution in the existing issues, docs, nor discussions I have joined the ZITADEL chat Describe your problem I tested the updated Helm Chart with LoginV2 but i...