GitHub user SnoozeFreddo edited a comment on the discussion: Bring my own
secret for postgresql connection
@pettermk This sadly didn't work. For some reason superset init container
spits
> /11/27 10:46:42 Problem with dial: dial tcp: lookup
> superset-apache-postgresql on 10.43.0.10:53: no such host. Sleeping 1s
2025/11/27 10:46:43 Timeout after 2m0s waiting on dependencies to become
available: [tcp://superset-apache-postgresql:5432]
out.
One solution is to replace the base environment from which the template gets
its values (envFromSecret: '{{ template "superset.fullname" . }}-env'), but
this causes other issues in my case . It seems like this superset init-db
container is just waiting for a connection, so I removed it by setting:
supersetNode:
initContainers: []
I also tried patching the DB_HOST variable, but that didn’t work for the init
container either.
I’m curious why this was implemented as an init container instead of a simple
“wait-for-it” script in the entrypoint before starting the main process. Does
the init container do anything besides waiting, or does it provide some
additional functionality?
GitHub link:
https://github.com/apache/superset/discussions/27916#discussioncomment-15095865
----
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]
