dosubot[bot] commented on issue #24521: URL: https://github.com/apache/superset/issues/24521#issuecomment-3325176481
<!-- Answer --> The root cause of missing example dashboards/tables after Helm upgrades in Superset on Kubernetes is usually tied to how the Helm chart handles database initialization and persistent storage. The Helm chart runs an init job on post-install and post-upgrade hooks to initialize the database and optionally load example data if `init.loadExamples` is set to `true` in your `values.yaml` file. If this flag is not enabled, or if your persistent database volume is lost or reset during upgrades, the example tables and dashboards will disappear, resulting in "no such table" errors. Running `superset load-examples` manually works because it repopulates the database after the fact, but this is only a temporary fix. To persist example data across upgrades, make sure: - Your metadata database (Postgres/MySQL) uses persistent storage (PVC) and is not reset or reinitialized during upgrades. - The `init.loadExamples` flag is set to `true` in your Helm chart configuration so the init job loads examples after every upgrade or install. - You monitor the logs of the init job for errors and confirm that the example tables are created successfully. If you are using SQLite as the backend, consider switching to Postgres or MySQL, as SQLite is more prone to issues in containerized environments. This is not a Superset application bug, but rather a deployment/configuration issue with the Helm chart and persistent storage setup. Improving documentation around Helm chart lifecycle and persistent storage could help avoid confusion for future users. For more details, see the [Helm chart values.yaml and init job logic](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/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f848c6ca-0431-4c3b-ba89-a9a0fcbcf013?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu b) [](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/issues/24521) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
