GitHub user dosubot[bot] added a comment to the discussion: Production deployment issue in
<!-- Answer --> The "dial tcp ... i/o timeout" error from nginx ingress usually means the ingress controller can't reach your Superset service inside the cluster. This is almost always a cluster networking, pod readiness, or firewall issue—not a problem with your values.yaml or the Superset Helm chart itself, which follows standard Kubernetes conventions for service and ingress wiring ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/README.md)). Here's how to troubleshoot: 1. **Check that the nginx ingress controller pod is running and healthy**: ``` kubectl get pods -n <ingress-namespace> kubectl logs <nginx-ingress-pod> -n <ingress-namespace> ``` If the pod isn't running, or logs show errors, the ingress can't route traffic. 2. **Check that the Superset service has endpoints and the pod is Ready**: ``` kubectl get endpoints superset -n superset kubectl get pods -n superset ``` The endpoints output should show the pod IP(s). If it's empty, your pod isn't Ready or the service selector doesn't match. 3. **Check for network policies or firewalls**: If you're on AKS, make sure there are no NetworkPolicies or NSGs blocking traffic between the ingress controller and the Superset pod/service. 4. **Check nginx ingress controller logs for backend errors**: ``` kubectl logs <nginx-ingress-pod> -n <ingress-namespace> ``` Look for errors about connecting to the backend service. 5. **Test connectivity from the ingress controller pod to the Superset service**: ``` kubectl exec <nginx-ingress-pod> -n <ingress-namespace> -- curl -v http://superset.superset.svc.cluster.local:8088/health ``` If this fails, it's a cluster networking issue. 6. **Verify the external IP is reachable and DNS resolves**: Make sure `superset.20.235.201.100.nip.io` resolves to your ingress external IP and is reachable from your client. If any of these checks fail, that's where the problem is. Most commonly, the service has no endpoints (pods not Ready), the ingress controller isn't running, or a network policy/firewall is blocking traffic. The Helm chart and values.yaml are correct as long as the service is type ClusterIP, port 8088, and the ingress points to the service on port "http" ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/templates/service.yaml)). Let me know what you find from these checks and I can help you narrow it down further. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/375ac069-b892-4985-8116-28edf2487f2a?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/33957) GitHub link: https://github.com/apache/superset/discussions/33957#discussioncomment-13801083 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
