JunseoChoJJ opened a new issue, #27838: URL: https://github.com/apache/superset/issues/27838
### Bug description I am working on installing superset on kubernetes. I have my own postgresql so my postgresql line 770 enable is false as well I got this issue when I'm running helm upgrade --install --values superset-helm.yaml superset superset/superset --debug one of my superset pod status is crashloopbackoff and when I put kubectl logs superset-worker-6585f4d54f-s4dxj I got this error  does anyone have idea for this?? I also changed security key as well ### How to reproduce the bug 1. Go to community ### Screenshots/recordings _No response_ ### Superset version 3.1.1 ### Python version Not applicable ### Node version I don't know ### Browser Chrome ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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.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
