You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/18 02:52:02 UTC
[jira] [Updated] (AIRFLOW-3917) Support for running Airflow
scheduler(with KubernetesExecutor) outside of K8 cluster
[ https://issues.apache.org/jira/browse/AIRFLOW-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-3917:
--------------------------------------------
Labels: kubernetes (was: )
Adding executor component, and kubernetes label as part of component refactor.
> 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
> Labels: kubernetes
> Fix For: 1.10.3
>
>
> 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)