[Question] Unable to access on first installation. #4040
Description
General Question
Hello, I'm excited to be exploring Zadig. I'm currently trying to use it, but I find the Helm-based installation guide in the official documentation a bit lacking in detail. As a result, while I was able to successfully install the Zadig cluster, I'm unable to access it.
During the Helm installation steps, many parts are overly simplified, and when issues arise, it’s difficult to know where to start troubleshooting.
Let me describe my situation:
I’m using k3s to install a single-node Kubernetes cluster (version 1.31). The cluster includes the built-in Traefik Ingress and Klipper service LoadBalancer. I used Helm to install Zadig with the following:
endpoint:
# endpoint.type is the type of Zadig system endpoint. It can be of type FQDN or IP. By default the type is FQDN.
type: FQDN
# FQDN is the domain name the user choose to visit in. It must be set if endpoint is of type FQDN.
FQDN: zadig.whg.cn
dex:
fullnameOverride: zadig-dex
config:
issuer: http://zadig-dex:5556/dex
staticClients:
- id: zadig
redirectURIs:
- "http://zadig.whg.cn/api/v1/callback"
name: "zadig"
secret: ZXhhbXBsZS1hcHAtc2VjcmV0
After installation, all Pods started normally. The gateway-proxy service is of type LoadBalancer and successfully obtained an external IP:：
I mapped the domain name to this IP on my local machine, but I still can't access the service through the domain. What's even more puzzling is that I can't even telnet to port 80 or 443 of the service.
During my investigation, I noticed that Zadig uses the Solo.io stack under the hood. I briefly looked into it and discovered that Zadig relies on Gloo version 1.9, whereas the current Gloo documentation covers versions 1.17–1.18. Since I’m unfamiliar with Gloo, I eventually gave up digging further.
What I want to say is: if Zadig used a more common Ingress controller like nginx-ingress or traefik-ingress, I could probably figure it out. But since the project uses Gloo, I’m now stuck. And when I return to the documentation and all it says is “route traffic to the gateway-proxy service after installation,” I honestly feel hopeless.
During my research, I’ve gone through nearly all the available documentation and now have a good understanding of Zadig’s features. The functional documentation is quite detailed, but I’m confused as to why the installation instructions are so simple. I don’t quite understand the rationale behind this, and frankly, I’m already considering giving up on using Zadig.
I really appreciate the kind of installation guides provided by projects like rancher or calico — they offer thorough, beginner-friendly steps and clear explanations.