You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "pzecon (via GitHub)" <gi...@apache.org> on 2026/08/11 12:02:12 UTC
[D] Helm chart: No option to disable deployment-worker.yaml [superset]
GitHub user pzecon created a discussion: Helm chart: No option to disable deployment-worker.yaml
Currently, it is possible to bring your own PostgreSQL and/or Redis instance and disable deployment of the bundled dependencies via `.Values.postgresql.enabled` and `.Values.redis.enabled`, respectively.
This partially reflects the [documented superset architecture](https://superset.apache.org/admin-docs/6.1.0/installation/architecture), where redis and celery workers are optional. However, there is currently no option to disable rendering of `deployment-worker.yaml`. As a result, the chart still creates a superset worker `Deployment` even when Redis is disabled.
Could you add a `.Values.supersetWorker.enabled` option that conditionally disables rendering of the worker resources entirely?
As a workaround, I am currently setting:
```yaml
supersetWorker:
replicas:
replicaCount: 0
autoscaling:
enabled: false
```
This prevents worker pods from being created, but the worker deployment and its Redis-dependent configuration are still part of the rendered helm release.
GitHub link: https://github.com/apache/superset/discussions/43061
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Helm chart: No option to disable deployment-worker.yaml [superset]
Posted by "pzecon (via GitHub)" <gi...@apache.org>.
GitHub user pzecon edited a discussion: Helm chart: No option to disable deployment-worker.yaml
Currently, it is possible to bring your own PostgreSQL and/or Redis instance and disable deployment of the bundled dependencies via `.Values.postgresql.enabled` and `.Values.redis.enabled`, respectively.
This partially reflects the [documented superset architecture](https://superset.apache.org/admin-docs/6.1.0/installation/architecture), where redis and celery workers are optional. However, there is currently no option to disable rendering of `deployment-worker.yaml`. As a result, the chart still creates a superset worker `Deployment` even when Redis is disabled.
Could you add a `.Values.supersetWorker.enabled` option that conditionally disables rendering of the worker resources entirely?
As a workaround, I am currently setting:
```yaml
supersetWorker:
replicas:
replicaCount: 0
```
This prevents worker pods from being created, but the worker deployment and its Redis-dependent configuration are still part of the rendered helm release.
GitHub link: https://github.com/apache/superset/discussions/43061
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Helm chart: No option to disable deployment-worker.yaml [superset]
Posted by "pzecon (via GitHub)" <gi...@apache.org>.
GitHub user pzecon added a comment to the discussion: Helm chart: No option to disable deployment-worker.yaml
Thanks for your quick reply! I'm moving to the operator now :+1:
GitHub link: https://github.com/apache/superset/discussions/43061#discussioncomment-17989822
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Helm chart: No option to disable deployment-worker.yaml [superset]
Posted by "pzecon (via GitHub)" <gi...@apache.org>.
GitHub user pzecon closed a discussion: Helm chart: No option to disable deployment-worker.yaml
Currently, it is possible to bring your own PostgreSQL and/or Redis instance and disable deployment of the bundled dependencies via `.Values.postgresql.enabled` and `.Values.redis.enabled`, respectively.
This partially reflects the [documented superset architecture](https://superset.apache.org/admin-docs/6.1.0/installation/architecture), where redis and celery workers are optional. However, there is currently no option to disable rendering of `deployment-worker.yaml`. As a result, the chart still creates a superset worker `Deployment` even when Redis is disabled.
Could you add a `.Values.supersetWorker.enabled` option that conditionally disables rendering of the worker resources entirely?
As a workaround, I am currently setting:
```yaml
supersetWorker:
replicas:
replicaCount: 0
```
This prevents worker pods from being created, but the worker deployment and its Redis-dependent configuration are still part of the rendered helm release.
GitHub link: https://github.com/apache/superset/discussions/43061
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Helm chart: No option to disable deployment-worker.yaml [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
GitHub user rusackas added a comment to the discussion: Helm chart: No option to disable deployment-worker.yaml
The helm charts are likely to be deprecated in the imminent future. We'd highly recommend [migrating to the Kubernetes Operator](https://apache.github.io/superset-kubernetes-operator/user-guide/migration/), which will be the gold standard going forward.
GitHub link: https://github.com/apache/superset/discussions/43061#discussioncomment-17980469
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org