This is an automated email from the ASF dual-hosted git repository. kaxilnaik pushed a commit to branch v3-0-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit ead8990c2ef0546be0346bdea02c354ba53cd477 Author: Amogh Desai <[email protected]> AuthorDate: Thu Apr 17 15:21:11 2025 +0530 Fix broken link for CeleryKubernetesExecutor upgrade (#49391) (cherry picked from commit 8761bf895d3e6896a018ba4f2ff740c9fd43e07c) --- .../docs/administration-and-deployment/production-deployment.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/airflow-core/docs/administration-and-deployment/production-deployment.rst b/airflow-core/docs/administration-and-deployment/production-deployment.rst index 86558091ed6..be16876d6cc 100644 --- a/airflow-core/docs/administration-and-deployment/production-deployment.rst +++ b/airflow-core/docs/administration-and-deployment/production-deployment.rst @@ -179,7 +179,7 @@ of the executor you use: are managed by the Kubernetes cluster and will be automatically adopted by ``Schedulers`` when they are upgraded and restarted. -* For the :doc:``CeleryKubernetesExecutor <apache-airflow-providers-celery:celery_kubernetes_executor>``, you follow the +* For the :doc:`CeleryKubernetesExecutor <apache-airflow-providers-celery:celery_kubernetes_executor>`, you follow the same procedure as for the ``CeleryExecutor`` - you put the workers in offline mode, wait for the running tasks to complete, upgrade the workers, and then upgrade the scheduler, triggerer and webserver in a rolling restart mode - which should also adopt tasks run via the ``KubernetesExecutor`` part of the
