Zitadel in Kubernetes and access from within the cluster
⚙️Configuration🏬Self-hosted⛓️💥APIs❓Question✅Solved
Hi! I'm trying to set up Zitadel running in Kubernetes and having trouble with domain-based instance identification. I can access the admin UI and make API calls using the external domain; all good.
Now, I also want to make calls to Zitadel from within the cluster (using the
Trying to access the internal endpoint from within a temporary pod:
...which is fair enough, but how do I fix that?
( also, it says 'https' there, but I'm using http as it's internal comms )
- I read all the docs, helm chart specs, config specs, github tickets and tutorials I could find
-
- adding extra domains to the Organisation doesn't change anything ( I tried all variants, with and without the port; they go straight into Verified domains as I have verification disabled )
- Helm
This is self-hosted K8S, latest Zitadel version deployed using the official Helm chart from charts.zitadel.com.
Now, I also want to make calls to Zitadel from within the cluster (using the
...svc.cluster.local...svc.cluster.local Service endpoint) and... I'm stuck.Trying to access the internal endpoint from within a temporary pod:
...which is fair enough, but how do I fix that?
( also, it says 'https' there, but I'm using http as it's internal comms )
- I read all the docs, helm chart specs, config specs, github tickets and tutorials I could find
-
/ui/console/instance?id=domain/ui/console/instance?id=domain doesn't offer adding new domains- adding extra domains to the Organisation doesn't change anything ( I tried all variants, with and without the port; they go straight into Verified domains as I have verification disabled )
- Helm
zitadel.selfSignedCert.additionalDnsNamezitadel.selfSignedCert.additionalDnsName seems to be for the cert onlyThis is self-hosted K8S, latest Zitadel version deployed using the official Helm chart from charts.zitadel.com.
