You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2020/01/19 23:18:00 UTC

[jira] [Commented] (AIRFLOW-3936) Support for emptyDir volume in KubernetesExecutor

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

Jarek Potiuk commented on AIRFLOW-3936:
---------------------------------------

[~dimberman] - > should we close that one?

> Support for emptyDir volume in KubernetesExecutor
> -------------------------------------------------
>
>                 Key: AIRFLOW-3936
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3936
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: executors, scheduler
>    Affects Versions: 1.10.1
>            Reporter: raman
>            Priority: Major
>              Labels: kubernetes
>
> Currently It seems that K8 Executor expects the dags_volume_claim or git_repo to be always defined through airflow.cfg. Otherwise it does not come up.
> Though there is support for "emptyDir" volume in worker_configuration.py but kubernetes_executor fails in _validate function if these configs are not defined.
> Our dag files are stored in some remote location which can be synced to worker pod through init/side-car container. We are exploring if it makes sense to allow K8 executor to come up for cases where dags_volume_claim are git_repo are not defined. In such cases worker pod would look for the dags in emptyDir and worker_airflow_dags path (like it does for git-sync). Dag files can be made available in worker_airflow_dags path through init/side-car container.
>  



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