Kubernetes and Login V2
Apologies if this question has been asked already.
I have spun up Zitadel on my kubernetes cluster but im running into an issue when it comes to accessing the console. Any time I try accessing my domain (zitadel.example.com) I get redirected to
/ui/v2/login/login?authRequest=V2_337889696480756170 with only {"code":5, "message":"Not Found"} displaying on the page. The health endpoint returns fine as well as the console logs show no errors.
Any ideas, I've seen that potentially something isn't spinning up, but the documentation for kubernetes is lacking atm.2 Replies
Hi @Helix, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. [v2 login not found on fresh install (v4-rc.2) ] (1) :
This discusses similar issues with v2 login returning "Not Found" errors on fresh v4 installations and mentions that v4-rc3 had known issues with this problem.
2. [Login app in kubernetes (localhost:3000, docker) ] (2) :
This covers deployment challenges with the TypeScript login app in Kubernetes environments, including issues with header forwarding that can cause incorrect redirects.
To learn more, see the sources I considered:
[1] v2 login not found on fresh install (v4-rc.2)
[2] Login app in kubernetes (localhost:3000, docker)
Feel free to tag @Ask Inkeep with additional questions.