GitHub user dosubot[bot] added a comment to the discussion: Custom image and helm deployment
<!-- Greeting --> Hi @ytihianine! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> The Helm chart for Superset always mounts a Kubernetes Secret at `/app/pythonpath`, which overrides any `superset_config.py` you include in your custom image. This is done by design using the `superset-config` template in the chart, and there is no built-in flag to disable this behavior or use only the file from your image ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/templates/_helpers.tpl)). To use your own config, create a Kubernetes Secret containing your custom `superset_config.py`, then set the `configFromSecret` value in your Helm values file to the name of that Secret. The chart will mount your Secret instead of the default generated config ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/README.md)). For example: ```bash kubectl create secret generic my-superset-config \ --from-file=superset_config.py=./superset_config.py ``` Then in your `values.yaml`: ```yaml configFromSecret: my-superset-config ``` If you only need to append or override a few settings, you can use the `configOverrides` or `configOverridesFiles` values, but these are appended to the generated config and do not replace it entirely. There is currently no supported way to prevent the Helm chart from mounting a config Secret at `/app/pythonpath` ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/values.yaml)). <!-- 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/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0d77c69e-0fa7-4813-bfaf-21cf07851d94?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-14225371 ---- 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
