GitHub user NiklasRosenstein added a comment to the discussion: superset helm 0.15.0 chart broken
I'm also running into this issue. And to @rusackas point, I've run into it before two years ago already: https://github.com/apache/superset/issues/23577 (note how I had to install `psycopg2` in the `bootstrapScript`). I get this error not when connecting to an external database. It seems reasonable to require installing additional drivers in some way explicitly for various reasons (e.g. license, image bloat, maintenance, etc.). The error appears with when the Pods try to connect to the **internal** Postgres DB... <img width="805" height="182" alt="Image" src="https://github.com/user-attachments/assets/c23d2660-15cc-4a55-871d-63163d7d052c"; /> <img width="876" height="128" alt="Image" src="https://github.com/user-attachments/assets/1ba86a85-f302-47c0-b678-6caf6c87765b"; /> We're looking to evaluate Superset against other (some not open source) competitors in the space, but this doesn't exactly inspire confidence in the project unfortunately. ```yaml # helmfile.yaml repositories: - name: superset url: https://apache.github.io/superset releases: - name: superset namespace: superset chart: superset/superset version: "0.15.0" values: # Bitnami has moved their container images behind a paywall. The Superset Helm charts have not been updated yet. # See https://github.com/apache/superset/issues/34414#issuecomment-3307806333 - postgresql: image: repository: bitnamilegacy/postgresql redis: image: repository: bitnamilegacy/redis - configOverrides: secret: | SECRET_KEY = 'CHANGE_ME_TO_A_SECRET' ``` If Postgres is the default database of choice, it doesn't make sense IMO to exclude the `psycopg2` driver that is obviously needed from the image. At the very least, the Kubernetes deployment documentation could provide the steps to install the driver e.g. via `bootstrapScript`. Note how https://superset.apache.org/docs/installation/kubernetes/#dependencies mentions that additional drivers may need to be installed, but only on the topic of connecting to external databases, _not_ for Superset to actually be coming up healthy. <img width="897" height="338" alt="Image" src="https://github.com/user-attachments/assets/1615fda0-f31c-4d5e-b3c1-a85536b6e84c"; /> Interestingly, the Postgres section here (https://superset.apache.org/docs/configuration/databases/#postgres) mentions that the driver comes pre-installed when using docker-compose. Then why not with Kubernetes? <img width="864" height="245" alt="Image" src="https://github.com/user-attachments/assets/45b5ee8c-e617-43c7-873f-91dba0821b10"; /> GitHub link: https://github.com/apache/superset/discussions/42584#discussioncomment-17832840 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
