[ 
https://issues.apache.org/jira/browse/AIRFLOW-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858671#comment-16858671
 ] 

ASF subversion and git services commented on AIRFLOW-4585:
----------------------------------------------------------

Commit d798df7e3438ae219b76de35ca581e8d6fb98aa2 in airflow's branch 
refs/heads/v1-10-test from Philippe Gagnon
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=d798df7 ]

[AIRFLOW-4585] Implement Kubernetes Pod Mutation Hook (#5359)

(cherry picked from commit 5899cec01e0ea69a54e650a9e1abdbcd5370e120)


> Implement pod mutation hook for KubernetesExecutor and KubernetesPodOperator
> ----------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4585
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4585
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: executors
>    Affects Versions: 1.10.3
>            Reporter: Philippe Gagnon
>            Assignee: Philippe Gagnon
>            Priority: Major
>              Labels: executor, kubernetes
>             Fix For: 1.10.4
>
>
> This is a proposal to add a mutation hook similar to the {{policy}} function 
> in {{airflow_local_settings}} to allow cluster administrators to mutate 
> worker pods with more complex behavior than what is currently possible with 
> the ini-based configuration.
> This function could be called in {{PodLauncher.run_pod\{_async}}} and apply 
> cluster-wide mutations to pods. This could for instance allow users to add 
> complex sidecar or init containers to pods launched by their Airflow instance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to