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

ASF GitHub Bot commented on AIRFLOW-2770:
-----------------------------------------

feng-tao opened a new pull request #4318: Revert  [AIRFLOW-2770] [AIRFLOW-3505]
URL: https://github.com/apache/incubator-airflow/pull/4318
 
 
   The k8s CI seems to be broken after 
https://github.com/apache/incubator-airflow/pull/3683 is merged(although local 
pr test if pass. suspect the pr doesn't rebase with master)
   
   Revert the prs to unblock CI. @dimberman will do some investigations before 
we re-push the change.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> kubernetes: add support for dag folder in the docker image
> ----------------------------------------------------------
>
>                 Key: AIRFLOW-2770
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2770
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Rurui Ye
>            Assignee: Rurui Ye
>            Priority: Critical
>             Fix For: 1.10.2
>
>
> currently the kube executor need to provider dag_volume_chain or git repo in 
> the config file, but if the user has build dag into their docker image, they 
> doesn't need to provider these two options, and they can manager their dag 
> version by manager the docker image version. 
> So I suppose we can add the a new configuration as 
> kube.config.dag_folder_path along with dag_volume_chain and git repo. with 
> this config, we can run the worker just from the dags in docker image.



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

Reply via email to