Skip to content

Remove mention of CeleryKubernetesExecutor from KubernetesExecutor doc #73624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shahar1 merged 4 commits into from
Sep 24, 2026
Merged

Remove mention of CeleryKubernetesExecutor from KubernetesExecutor doc #73624

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8ac96ba
Removed mention of CeleryKubernetesExecutor from KubernetesExecutor d…
alant94 Sep 23, 2026
77f4449
Enhance documentation on executor usage
alant94 Sep 23, 2026
5d8d3f6
Fix link formatting in kubernetes_executor
alant94 Sep 23, 2026
d62482a
Merge branch 'main' into patch-1
alant94 Sep 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions providers/cncf/kubernetes/docs/kubernetes_executor.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---------------
Expand Down