login-client & iam-admin secrets are not created when deploying using helm
🏬Self-hosted🪲Bugs✅Solved
Use-case: I just want to deploy Zitadel using helm. Actually just following the tutorial for now: https://zitadel.com/docs/self-hosting/deploy/kubernetes/installation
Environment: Self hosted, empty env
Version: The latest (CHART VERSION: 9.23.0; APP VERSION: v4.10.1)
Stack: Nothing right now. Have an external db and nothing else. Trying to deploy it. Only thing I am doing different than the tutorial is using nginx ingress, but I doubt it is the cause of the issue.
What you expected to happen: Would like the login pod to actually start at some point.
Attachments:
description shows:
Indeed the secret is not created.
Note: I tried to disable login v2 in the helm chart. It is indeed not deployed, but the redirection is still made by zitadel.
Environment: Self hosted, empty env
Version: The latest (CHART VERSION: 9.23.0; APP VERSION: v4.10.1)
Stack: Nothing right now. Have an external db and nothing else. Trying to deploy it. Only thing I am doing different than the tutorial is using nginx ingress, but I doubt it is the cause of the issue.
What you expected to happen: Would like the login pod to actually start at some point.
Attachments:
description shows:
Warning FailedMount 78s (x15 over 15m) kubelet MountVolume.SetUp failed for volume "login-client" : secret "login-client" not foundIndeed the secret is not created.
iam-adminNote: I tried to disable login v2 in the helm chart. It is indeed not deployed, but the redirection is still made by zitadel.
Deploy ZITADEL on Kubernetes using Helm with a PostgreSQL database and an Ingress controller for external access
