You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ep...@apache.org on 2022/11/09 20:23:00 UTC
[airflow] 17/29: Document that KubernetesExecutor overwrites container args (#27450)
This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v2-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 1c6de53b7f1a7d89ac1010633a8012a64a6d6afe
Author: Jed Cunningham <66...@users.noreply.github.com>
AuthorDate: Tue Nov 1 23:08:45 2022 -0700
Document that KubernetesExecutor overwrites container args (#27450)
The executor will overwrite the args for the container so that the
worker runs the right task.
(cherry picked from commit 8f5e100f30764e7b1818a336feaa8bb390cbb327)
---
docs/apache-airflow/executor/kubernetes.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow/executor/kubernetes.rst b/docs/apache-airflow/executor/kubernetes.rst
index e24582c7df..e5c1fc3d09 100644
--- a/docs/apache-airflow/executor/kubernetes.rst
+++ b/docs/apache-airflow/executor/kubernetes.rst
@@ -126,7 +126,7 @@ pod_override
When using the KubernetesExecutor, Airflow offers the ability to override system defaults on a per-task basis.
To utilize this functionality, create a Kubernetes V1pod object and fill in your desired overrides.
-Please note that the scheduler will override the ``metadata.name`` of the V1pod before launching it.
+Please note that the scheduler will override the ``metadata.name`` and ``containers[0].args`` of the V1pod before launching it.
To overwrite the base container of the pod launched by the KubernetesExecutor,
create a V1pod with a single container, and overwrite the fields as follows: