GitHub user dosubot[bot] added a comment to the discussion: Custom image and helm deployment
<!-- Answer --> The Superset Helm chart always generates and mounts its own superset_config.py at /app/pythonpath, which overrides any config you bake into your image—even if you set SUPERSET_CONFIG_PATH. This is why your custom config works locally but not with Helm. There’s no supported way to merge your image config with the Helm-generated defaults. The chart expects to control the main config file and builds things like SQLALCHEMY_DATABASE_URI and Redis settings from Helm values, not from your config file ([source](https://github.com/apache/superset/issues/33945)). If you want to combine your custom settings (like APP_ICON) with the Helm defaults, the recommended pattern is to use the configOverrides or configOverridesFiles values in your Helm values.yaml. These let you append Python code to the generated config. For example: ```yaml configOverrides: | APP_ICON = "/static/assets/local/images/app_icon.png" ``` If you need more complex logic, you can use configOverridesFiles to mount a Python file with your custom code, and then import it at the end of the generated config. If you want to fully control the config, you can create a Kubernetes Secret with your own superset_config.py and set configFromSecret to its name. But then you must include all required settings (like SQLALCHEMY_DATABASE_URI) yourself, since you’ll be bypassing the Helm defaults ([source](https://github.com/apache/superset/issues/33945)). There’s no built-in way to have the Helm chart “merge” your image config with its own defaults—the only supported options are to append code via configOverrides or to fully replace the config via a Secret. <!-- 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/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7f8c0692-3232-433d-b3e4-6252768cb762?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/34861) GitHub link: https://github.com/apache/superset/discussions/34861#discussioncomment-14225650 ---- 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
