You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (Jira)" <ji...@apache.org> on 2021/05/05 08:34:00 UTC

[jira] [Closed] (AIRFLOW-7091) use external worker pod template

     [ https://issues.apache.org/jira/browse/AIRFLOW-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor closed AIRFLOW-7091.
--------------------------------------
    Resolution: Not A Bug

1.10.9 didn't include this feature, only 1.10.14+

> use external worker pod template
> --------------------------------
>
>                 Key: AIRFLOW-7091
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-7091
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler, worker
>    Affects Versions: 1.10.9
>            Reporter: Hicham
>            Priority: Critical
>
>  I am trying to use my own pod template file with KubernetesExecutor. So, in the official documentation of airflow.cfg, there's a reference that we can use external pod template
> {code:java}
> # Path to the YAML pod file. If set, all other kubernetes-related fields are ignored.
> pod_template_file = /path/to/file{code}
> I tried to use it by specifying the path to a pod template file, but it's not working at all as the scheduler cannot launch workers.
> Do you have any ideas how can I use it or how to solve this? Thank you.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)