[
https://issues.apache.org/jira/browse/AIRFLOW-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793576#comment-16793576
]
ASF subversion and git services commented on AIRFLOW-3917:
----------------------------------------------------------
Commit c7d640bb6a8edc21c6db5107d39bbfeff1a72169 in airflow's branch
refs/heads/master from raman
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c7d640b ]
[AIRFLOW-3917] Specify alternate kube config file/context when running out of
cluster (#4859)
> Support for running Airflow scheduler(with KubernetesExecutor) outside of K8
> cluster
> ------------------------------------------------------------------------------------
>
> Key: AIRFLOW-3917
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3917
> Project: Apache Airflow
> Issue Type: Improvement
> Components: executor, kubernetes, scheduler
> Affects Versions: 1.10.1, 1.10.2
> Reporter: raman
> Assignee: raman
> Priority: Major
>
> Currently It seems that Airflow Scheduler needs to be run inside K8 cluster
> as a long running pod.
> Though there is "in_cluster" config exposed through airflow.cfg but there
> does not seem to be a provision to pass required config file while creating
> kube_client.
> Following is the code snippet from kubernetes_executor.py's start function
> where kube_client is configured without passing any config
> self.kube_client = get_kube_client()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
