himanshuchawla0807-gif commented on code in PR #74913:
URL: https://github.com/apache/airflow/pull/74913#discussion_r4312169631
##########
chart/docs/customizing-workers.rst:
##########
@@ -32,6 +32,50 @@ For example, to set resources on workers for CeleryExecutor:
limits:
cpu: 1
+Separate Celery worker sets
+---------------------------
+
+Use ``workers.celery.sets`` to configure workers for different queues. Each set
+inherits ``workers.celery`` settings and can override them, including
+``extraVolumes`` and ``extraVolumeMounts``. For example, mount different
existing
+PersistentVolumeClaims for two worker sets:
+
+.. code-block:: yaml
+ :caption: values.yaml
+
+ executor: CeleryExecutor
+ workers:
+ celery:
+ enableDefault: false
+ sets:
+ - name: analytics
+ queue: analytics
+ extraVolumes:
+ - name: input-data
+ persistentVolumeClaim:
+ claimName: analytics-input
+ extraVolumeMounts:
+ - name: input-data
+ mountPath: /opt/airflow/input
+ readOnly: true
+ - name: research
+ queue: research
+ extraVolumes:
+ - name: input-data
+ persistentVolumeClaim:
+ claimName: research-input
+ extraVolumeMounts:
+ - name: input-data
+ mountPath: /opt/airflow/input
+ readOnly: true
+
+Create both PersistentVolumeClaims before deploying the chart, and route tasks
Review Comment:
Addressed in c05e6f13fc: the example now explains inherited
replicas/autoscaling and recommends multi-node read-only access such as
`ReadOnlyMany` with a compatible storage driver.
---
Drafted-by: OpenAI Codex (no human review before posting)
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
