GitHub user Kranthi32 added a comment to the discussion: Production deployment 
issue in

@dosu [@dosu](https://go.dosu.dev/dosubot).  getting anoter issue as per u 
suggested only i mentioned configuration but what is this how to resolve


 kubectl logs superset-init-db-9r4jz -n superset --all-containers=true
Upgrading DB schema...
logging was configured successfully
2025-06-27 17:30:49,879:INFO:superset.utils.logging_configurator:logging was 
configured successfully
2025-06-27 17:30:49,883:INFO:root:Configured event logger of type <class 
'superset.utils.log.DBEventLogger'>
We haven't found any Content Security Policy (CSP) defined in the 
configurations. Please make sure to configure CSP using the TALISMAN_ENABLED 
and TALISMAN_CONFIG keys or any other external software. Failing to configure 
CSP have serious security implications. Check 
https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for more information. You 
can disable this warning using the CONTENT_SECURITY_POLICY_WARNING key.
2025-06-27 17:30:49,884:WARNING:superset.initialization:We haven't found any 
Content Security Policy (CSP) defined in the configurations. Please make sure 
to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any 
other external software. Failing to configure CSP have serious security 
implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for 
more information. You can disable this warning using the 
CONTENT_SECURITY_POLICY_WARNING key.
Falling back to the built-in cache, that stores data in the metadata database, 
for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use 
`RedisCache`, `MemcachedCache` or another dedicated caching backend for 
production deployments
2025-06-27 17:30:49,886:WARNING:superset.utils.cache_manager:Falling back to 
the built-in cache, that stores data in the metadata database, for the 
following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use 
`RedisCache`, `MemcachedCache` or another dedicated caching backend for 
production deployments
Falling back to the built-in cache, that stores data in the metadata database, 
for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to 
use `RedisCache`, `MemcachedCache` or another dedicated caching backend for 
production deployments
2025-06-27 17:30:49,891:WARNING:superset.utils.cache_manager:Falling back to 
the built-in cache, that stores data in the metadata database, for the 
following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use 
`RedisCache`, `MemcachedCache` or another dedicated caching backend for 
production deployments
2025-06-27 17:30:49,892:ERROR:flask_appbuilder.security.sqla.manager:DB 
Creation and initialization failed: (psycopg2.OperationalError) could not 
translate host name 
"[email protected]" to address: Name 
or service not known

(Background on this error at: https://sqlalche.me/e/14/e3q8)
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
2025/06/27 17:30:44 Waiting for: 
tcp://appsqlsscind01.private.postgres.database.azure.com:5432
2025/06/27 17:30:44 Connected to 
tcp://appsqlsscind01.private.postgres.database.azure.com:5432

GitHub link: 
https://github.com/apache/superset/discussions/33957#discussioncomment-13600099

----
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]

Reply via email to