GitHub user dosubot[bot] added a comment to the discussion: Cutom Docker Image Build and deplument via Helm
<!-- Answer --> A 504 from ALB usually means the load balancer can't reach your Superset backend in time. For Superset on Kubernetes via Helm, double-check these areas: - Your Helm values.yaml should have ingress enabled, with the correct ingressClassName for ALB, and ALB-specific annotations under ingress.annotations. The service type should be ClusterIP (default), and the service port should match what ALB expects (usually 8088) [chart config reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/values.yaml). - Make sure your Superset pods are healthy and responding to /health (the chart sets up readiness/liveness probes on this endpoint, which ALB uses for health checks) [probe config reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/values.yaml). - Set ALB-specific ingress annotations for timeouts, SSL, and routing in values.yaml. The chart exposes an annotations map for this, but you need to add the AWS-specific keys yourself [ingress template reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/templates/ingress.yaml). - Check that your ALB target group health checks are passing. If not, look at pod logs (`kubectl logs <pod>`) and describe the ingress/service for errors. - If you're using HTTPS, set WEBSERVER_BASE_URL, ENABLE_PROXY_FIX, SESSION_COOKIE_SECURE, and PREFERRED_URL_SCHEME in Superset config to match your ALB setup [discussion](https://github.com/apache/superset/discussions/31584). If you share your ingress section from values.yaml and clarify which ingress controller you're using, I can help spot any misconfigurations. <!-- 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/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/faa2caec-18d0-4f58-9c20-806ab5cd64a5?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-14410379 ---- 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
