HsiuChuanHsu opened a new pull request, #56589:
URL: https://github.com/apache/airflow/pull/56589
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
## Summary
This PR adds support for multiple Celery worker groups. Each group can now
be independently configured to target specific queues and use distinct resource
settings
> The goal is to achieve **fine-grained** control over task distribution by
assigning queues to specific worker nodes.
## Changes
**New Configuration**: `workers.celeryQueueGroups`
Added support for defining multiple worker deployments through the
`workers.celeryQueueGroups` configuration. Each group can specify:
- `name`: (required) Unique name for the worker group
- `queues`: (required) Comma-separated list of Celery queues
- `replicas`: (required) Number of worker replicas
- `nodeSelector`: (optional)
- `affinity`: (optional)
- `tolerations`: (optional)
- `topologySpreadConstraints`: (optional)
- `resources`: (optional)
- `labels`: (optional)
- `podAnnotations`: (optional)
- `priorityClassName`: (optional)
- `env`: (optional)
**`worker-deployment.yaml` Logic**
- Modified the worker deployment template to loop through all configured
worker groups
- For default behavior (no `celeryQueueGroups` defined), the template
maintains original setup using existing workers.* configuration
- Each worker group creates a separate Deployment/StatefulSet with:
- Unique name suffix based on group name (e.g.,
airflow-worker-high-priority)
- **worker-group** label for identification
- **Queue-specific command arguments**: `exec airflow celery worker
--queues <group-queues>`
- Custom resource configurations override default settings per group
**`worker-service.yaml` Logic**
- Extended service template to create separate services for each worker group
- Each service is scoped to its corresponding worker group using the
`worker-group` label selector
- Service naming follows the pattern: `{{ airflow.fullname
}}-worker-<group-name>`
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
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]
