GitHub user dosubot[bot] added a comment to the discussion: Cutom Docker Image Build and deplument via Helm
<!-- Answer --> Your Helm values.yaml looks correct for ALB integration: service type is ClusterIP on port 8088, ingress is enabled with ingressClassName set to "alb", and ALB-specific annotations are present. The chart maps these settings directly to the Kubernetes Ingress resource, so ALB should route traffic to your Superset pods if everything is healthy [values.yaml](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/values.yaml). Superset's readiness, liveness, and startup probes all target the /health endpoint on port 8088, which matches your ALB health check path and port. This setup is important for ALB to detect healthy pods and avoid 504 errors [deployment.yaml](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/templates/deployment.yaml). If you're still seeing 504 errors, check these next: - Are your Superset pods passing readiness and liveness probes? Run `kubectl get pods` and `kubectl describe pod <pod>` to confirm. - Is the ALB target group showing healthy targets? In AWS console, check the target group health status. - Does the /health endpoint return HTTP 200 from inside the cluster? You can test with `kubectl exec <pod> -- curl localhost:8088/health`. - Are there any errors in pod logs or events? Use `kubectl logs <pod>` and `kubectl describe ingress <ingress-name>`. Most 504s are caused by unhealthy pods, misconfigured health checks, or network/security group issues between ALB and your cluster. If all probes and health checks are passing, traffic should flow correctly. If not, focus on pod health and ALB target group diagnostics. <!-- 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/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0a3e9b1b-c20e-4e1d-8d70-1498307793c6?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/34882) GitHub link: https://github.com/apache/superset/discussions/34882#discussioncomment-14410476 ---- 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
