Update multi-node executor guidance (#48605)#69154
Conversation
shahar1
left a comment
shahar1
left a comment
There was a problem hiding this comment.
@deepujain please note that you (or your operator) should include AI attribution in the PR as we state in the AI guidelines.
This PR, as well as others, are blocked from being merged until this is corrected.
Please be warned that creating additional PRs except for the 10 you've already created (listed below) without addressing the above might cause in a permanent block from Apache organization on GitHub.
List of PRs:
potiuk
added
the
ready for maintainer review
potiuk
left a comment
potiuk
left a comment
There was a problem hiding this comment.
Docs-only — accurately broadens the multi-node executor guidance beyond Celery/Kubernetes. Verified the diff, links resolve. LGTM.
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
3 participants
Summary
Update the production deployment guide so multi-node deployments point readers to the current remote-executor and multi-executor guidance instead of naming only Celery and Kubernetes.
Changes
airflow-core/docs/administration-and-deployment/production-deployment.rst-- mention remote executors, multi-executor configuration, current executor examples, and the executor comparison.Test plan
git diff --checkprek run --stage pre-commit --files airflow-core/docs/administration-and-deployment/production-deployment.rstWas generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex following the guidelines
Fixes #48605