GitHub user dosubot[bot] added a comment to the discussion: Cutom Docker Image Build and deplument via Helm
<!-- Answer --> You can deploy Superset on Kubernetes using the official Helm chart, which is located in the `helm/superset` directory of the Superset GitHub repo. The public Helm chart registry is no longer available, so you should use the chart directly from the repo or host it internally in your organization. The chart is community-maintained and not officially supported by the core project, so thorough testing is recommended for production use [source](https://github.com/apache/superset/issues/34301). To deploy Superset 5.0.0, use Helm chart version 0.14.2 and override the image tag in your `values.yaml` to specify the 5.0.0 image. There isn't a chart version specifically for 5.0.0, so this approach requires extra validation [source](https://github.com/apache/superset/discussions/34312). The Helm chart provides static templates for Superset services, database, ingress, and persistent storage. You can disable the internal PostgreSQL database by setting `postgresql.enabled: false` in `values.yaml` and configure an external database via `supersetNode.connections`. Store sensitive credentials like database passwords securely using Kubernetes secrets [source](https://github.com/apache/superset/issues/33945). For custom images or extra connectors (like Trino), build your own Docker image with the required packages installed, push it to your registry, and update the Helm chart values to use your image [source](https://github.com/apache/superset/issues/33691). If you need to deploy Superset under a URL prefix, set `APPLICATION_ROOT`, `STATIC_ASSETS_PREFIX`, and `ENABLE_PROXY_FIX` in Superset config, and configure your ingress or nginx proxy accordingly [source](https://github.com/apache/superset/issues/33226). The Helm chart deployment applies manifests once and does not provide continuous reconciliation or advanced lifecycle management features like a Kubernetes operator [source](https://github.com/apache/superset/issues/31408). Let me know if you need example configs or have specific questions about customizing your deployment! <!-- 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/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a42f50da-1b68-4a0a-93f4-6d5b722aaffd?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-14254722 ---- 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
