Skip to content
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

volumeMounts for extraConfigs are missing in the deployment-worker.yaml #20828

Closed
cdreier opened this issue Jul 22, 2022 · 0 comments · Fixed by #20829
Closed

volumeMounts for extraConfigs are missing in the deployment-worker.yaml #20828

cdreier opened this issue Jul 22, 2022 · 0 comments · Fixed by #20829
Labels

Comments

@cdreier
Copy link
Contributor

cdreier commented Jul 22, 2022

Hi,

we try to run superset on kubernetes with your helm charts and a custom security manager. we use the extraConfigs to mount some config files needed by flask_oidc (client_secret.json) - in the superset node, everything is fine, but the worker node crashes as the worker also initializes the flask_oidc context and does not mount the extraConfigs

working deployment for the superset node

https://github.com/apache/superset/blob/master/helm/superset/templates/deployment.yaml#L111

missing extraConfigs in the worker node 😢

https://github.com/apache/superset/blob/master/helm/superset/templates/deployment-worker.yaml#L104

Expected results

the worker node mounts all the extraConfigs under the extraVolumeMounts like the main node

Actual results

the worker node crashes, as the extraConfigs were not mounted

@cdreier cdreier added the #bug Bug report label Jul 22, 2022
cdreier added a commit to cdreier/superset that referenced this issue Jul 22, 2022
craig-rueda pushed a commit that referenced this issue Jul 25, 2022
* #20828 adding extraConfig to worker deployment

* fixed missing condition in volume declaration

* bumped chart version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants