This is an automated email from the ASF dual-hosted git repository.
shahar1 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 035af46b166 Remove mention of CeleryKubernetesExecutor from
KubernetesExecutor doc (#73624)
035af46b166 is described below
commit 035af46b166e64977d786fc687fc856d2d24992b
Author: Aliaksei <[email protected]>
AuthorDate: Thu Sep 24 09:05:21 2026 +0300
Remove mention of CeleryKubernetesExecutor from KubernetesExecutor doc
(#73624)
---
providers/cncf/kubernetes/docs/kubernetes_executor.rst | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/providers/cncf/kubernetes/docs/kubernetes_executor.rst
b/providers/cncf/kubernetes/docs/kubernetes_executor.rst
index 50f68181dcf..7b9b96b7dc2 100644
--- a/providers/cncf/kubernetes/docs/kubernetes_executor.rst
+++ b/providers/cncf/kubernetes/docs/kubernetes_executor.rst
@@ -231,11 +231,9 @@ the task will keep running until it completes (or times
out, etc). But with Cele
task will only keep running up until the grace period has elapsed, at which
time the task will be terminated. Another scenario where
KubernetesExecutor can work well is when your tasks are not very uniform with
respect to resource requirements or images.
-Finally, note that it does not have to be either-or; with
CeleryKubernetesExecutor, it is possible to use both CeleryExecutor and
-KubernetesExecutor simultaneously on the same cluster.
CeleryKubernetesExecutor will look at a task's ``queue`` to determine
-whether to run on Celery or Kubernetes. By default, tasks are sent to Celery
workers, but if you want a task to run using KubernetesExecutor,
-you send it to the ``kubernetes`` queue and it will run in its own pod. And
KubernetesPodOperator can be used
-to similar effect, no matter what executor you are using.
+Finally, note that it does not have to be either-or; using the `Multiple
Executors Concurrently feature
+<https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/executor/index.html#using-multiple-executors-concurrently>`_,
+it is possible to use both CeleryExecutor and KubernetesExecutor
simultaneously on the same cluster.
Fault Tolerance
---------------
