-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm Chart does not work if you enable celery beat with extraConfigs #22105
Labels
#bug
Bug report
Comments
This is the stacktrace that results when the client_screts.json not being found:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you deploy to k8s with the official helm chart and do enable celery 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 celery 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 celery beat pod (kind of inconsistent as is basically the same flask app that needs to load).
How to reproduce the bug
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
celery beat pod should start as normal superset or superset-workers do
Actual results
celery beat pod goes into crash loop / refuses to start
Checklist
Make sure to follow these steps before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: