Support pass command as args in k8s executor - #10481
Conversation
|
@dimberman could you please take a look? thanks |
|
Hi ping, going forward we're actually going to be deleting all of the k8sexecutor airflow.cfg configs involved in pod creation. This is because as of 1.10.12 we allow users to generate pod_templates using yaml. Please see the PR here for simplification of k8sexecutor #10393 |
Thanks, will keep this in mind. |
|
@dimberman the command and args are dynamic, i.e. they could be different for each run, so the only way to customize this behavior from a pod template is to interpolate these parameters using a jinja template during runtime. I don't know if it is possible currently, but would cover more use cases more cleanly than this approach. E.g. a common use case not covered by this when the entrypoint relays the args to |
The current implementation overrides the image's entrypoint, which is less ideal. Users may want to use their own entrypoint to do additional setup and clean up, before and after the airflow tasks.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.