You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Brandon Willard (Jira)" <ji...@apache.org> on 2020/02/12 03:21:00 UTC
[jira] [Created] (AIRFLOW-6780) Use args Instead of command in
Kubernetes Executor Worker Pods
Brandon Willard created AIRFLOW-6780:
----------------------------------------
Summary: Use args Instead of command in Kubernetes Executor Worker Pods
Key: AIRFLOW-6780
URL: https://issues.apache.org/jira/browse/AIRFLOW-6780
Project: Apache Airflow
Issue Type: Bug
Components: executor-kubernetes
Affects Versions: 1.10.9, 1.10.8, 1.10.7
Reporter: Brandon Willard
Assignee: Daniel Imberman
The worker pods created by the Kubernetes Executor are hard-coded to use [the {{command}} field instead of {{args}}|[https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#notes]!|https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#notes]. The result is a worker pod that ignores its image's entry-point and prevents the standard means of executing container preparation code --- among other things.
This --- alongside the issues stated in [AIRFLOW-6778|https://issues.apache.org/jira/browse/AIRFLOW-6778] and [AIRFLOW-3126|https://issues.apache.org/jira/browse/AIRFLOW-3126] --- renders worker nodes virtually incompatible with a dynamic, shared DAGs volume (unless dependencies are installed in the image and never change).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)