This is an automated email from the ASF dual-hosted git repository.
vatsrahul1001 pushed a commit to branch v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit d62774ba2f922af4e59a7eb20d4a042af7e8032c
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Sun Jul 5 15:52:26 2026 +0200
[v3-3-test] Update multi-node executor guidance (#48605) (#69154) (#69388)
* Update multi-node executor guidance (#48605)
* Use accepted spelling for executor trade-offs
(cherry picked from commit 2c46d0b3c458f5592c8b736e36956fba49f2f0f8)
Co-authored-by: Deepak Jain <[email protected]>
---
.../docs/administration-and-deployment/production-deployment.rst | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
a/airflow-core/docs/administration-and-deployment/production-deployment.rst
b/airflow-core/docs/administration-and-deployment/production-deployment.rst
index e88b94d94ba..8e1258bb9da 100644
--- a/airflow-core/docs/administration-and-deployment/production-deployment.rst
+++ b/airflow-core/docs/administration-and-deployment/production-deployment.rst
@@ -57,8 +57,13 @@ Multi-Node Cluster
==================
Airflow uses :class:`~airflow.executors.local_executor.LocalExecutor` by
default. For a multi-node setup,
-you should use the :doc:`Kubernetes executor
<apache-airflow-providers-cncf-kubernetes:kubernetes_executor>` or
-the :doc:`Celery executor <apache-airflow-providers-celery:celery_executor>`.
+choose a remote executor, or a multi-executor configuration, that matches
where tasks should run.
+Common choices include the :doc:`Celery executor
<apache-airflow-providers-celery:celery_executor>`,
+the :doc:`Kubernetes executor
<apache-airflow-providers-cncf-kubernetes:kubernetes_executor>`,
+Amazon provider executors such as :doc:`Batch
<apache-airflow-providers-amazon:executors/batch-executor>`
+or :doc:`ECS <apache-airflow-providers-amazon:executors/ecs-executor>`, and the
+:doc:`Edge executor <apache-airflow-providers-edge3:edge_executor>`. See the
+:ref:`executor comparison <executor-types-comparison>` for the current list
and trade-offs.
Once you have configured the executor, it is necessary to make sure that every
node in the cluster contains