Repository navigation
[DOCS] Helm Chart : Differents Volumes/VolumeMount for each Celery Workers Sets #63179
Description
Description
Issue Description: Airflow Helm Chart - Different Volumes/VolumeMounts for Each Celery Worker Sets
The Apache Airflow Helm chart currently lacks native support for configuring distinct Volumes and VolumeMounts for multiple Celery worker sets (It can separate queues like high-priority or GPU workers but not assign different volumes to different workers).
While workers.extraVolumes and workers.extraVolumeMounts enable uniform mounts across all workers, specialized workloads require per-worker-set customization for different storage needs, such as data volumes.
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
boring-cyborg commentedon Mar 9, 2026
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Subham-KRLX commentedon Mar 9, 2026
@AlexisChowYuen, this is already supported. You can set different extraVolumes and extraVolumeMounts per worker set using workers.celery.sets
workers:
celery:
sets:
- name: gpu-workers
queue: "gpu"
extraVolumes:
- name: gpu-data
hostPath:
path: /mnt/gpu
extraVolumeMounts:
- name: gpu-data
mountPath: /data/gpu
Each entry in sets generates its own StatefulSet with its own volumes. See the workers.celery.sets section in values.yaml for more examples. This might be a documentation gap rather than a missing feature.
Miretpl commentedon Mar 10, 2026
Agreed with predecessor. In general, every field of the
workerssection can be overwritten in theworkers.celery.setssection and we have full test coverage of it too. It's true that this behaviour is not present in documentation, despite being mention in the release notes https://airflow.apache.org/docs/helm-chart/stable/release_notes.html#support-for-multiple-celery-worker-sets-in-the-helm-chart-58547 regarding this feature.shahar1 commentedon Jun 19, 2026
Feature exists:
workers.celery.setsoverrides parent worker fields (incl. extraVolumes) per set, shipped in #58547.Turning it into a docs issue.
[-]Helm Chart : Differents Volumes/VolumeMount for each Celery Workers Sets[/-][+][DOCS] Helm Chart : Differents Volumes/VolumeMount for each Celery Workers Sets[/+]