12/28/2022, 4:37 AM
Is there something I need to do in order to allow the traefik ingress manager to function properly with a stock install? I've deployed several helm charts I've used before on cloud provided Kubernetes, and it always works properly. Now when I deploy it to my fresh k3s cluster with one node, it gives me
Bad Gateway
And nothing else. I deployed an Ubuntu pod to test things out, and the service it's trying to connect to functions properly and I get the output from the pod while curl'ing the service DNS. It really feels like an issue between the ingress and the service. When I deploy an ingress with Helm it gives me the following errors within the Traefik pod.
time="2022-12-28T03:08:21Z" level=error msg="Skipping service: no endpoints found" providerName=kubernetes serviceName=test servicePort="&ServiceBackendPort{Name:,Number:80,}" ingress=test namespace=default
time="2022-12-28T03:08:22Z" level=error msg="Skipping service: no endpoints found" servicePort="&ServiceBackendPort{Name:,Number:80,}" providerName=kubernetes namespace=default ingress=test serviceName=test


12/28/2022, 4:57 AM
It says “no endpoints”, is it wrong? Are there any active endpoints for that service?
and no, Traefik works out of the box.


12/28/2022, 5:11 AM
Yeah, I can get the output properly when I curl the service via the IP or the DNS entry from within the cluster. I have an Ubuntu pod deployed to the cluster for debugging and I get everything properly from the service, the pod is alive and responding.
So, within the Ubuntu pod, I do
curl test.default.svc.cluster.local
and I get the proper output