[
https://issues.apache.org/jira/browse/AIRFLOW-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126870#comment-17126870
]
ASF GitHub Bot commented on AIRFLOW-6780:
-----------------------------------------
brandonwillard commented on pull request #8146:
URL: https://github.com/apache/airflow/pull/8146#issuecomment-639558613
Just rebased.
One important use-case involves the ease of running pods with
important/necessary pre-specified `command`s. In general, no one wants to
re-produce a `Dockerfile`'s `command` string within the Airflow setup/pod spec,
since that's fairly cumbersome and error prone.
Plus, this problem is exacerbated by "derived" Docker images that pass
`args` to the parent image's `command`. I believe that—in these
cases—one would have to reproduce the parents' cumulative `command` and
`args`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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.7, 1.10.8, 1.10.9
> Reporter: Brandon Willard
> Assignee: Daniel Imberman
> Priority: Blocker
>
> 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)
