sker65 opened a new issue, #22105: URL: https://github.com/apache/superset/issues/22105
If you deploy to k8s with the official helm chart and do enable celebry beat pod for scheduled email reports the pod spec does not include extraConfigs if you configured any. This leads to a crash loop as the celebry beat pod refuses to start, if the flask app is somehow dependent on this extra config. While is is included in the worker pods, it is not in the celebry beat pod (kind of inconsistent as is basically the same flask app that needs to load). #### How to reproduce the bug 1. create an extra config the includes a file (in my example it is the client_secret.json, that the customSecurityManager want to load at startup time). 2. Add a celebry config like described in the example here: https://superset.apache.org/docs/installation/alerts-reports/ 3. Activate the celebry beat like describe in doc over here: https://superset.apache.org/docs/installation/alerts-reports/ 4. Try to apply the helm chart 5. The celebry start command will as soon as it tries to load the app see also https://github.com/apache/superset/blob/master/helm/superset/templates/deployment-beat.yaml (extraConfigs section missing in template) vs https://github.com/apache/superset/blob/master/helm/superset/templates/deployment-worker.yaml#L109 (extraConfigs included if set) ### Expected results celebry beat pod should start as normal superset or superset-workers do ### Actual results celebry beat pod goes into crash loop / refuses to start ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [X] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [X] I have reproduced the issue with at least the latest released version of superset. - [X] I have checked the issue tracker for the same issue and I haven't found one similar. -- 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
