Hey All, Currently it seems that Airflow scheduler with K8 executor mode is required to run inside K8 cluster. We are working on a use case where Airflow scheduler might run outside of K8 cluster. There is a boolean flag "in_cluster" exposed via airflow.cfg but there does not seem to be a way to provide cluster_context/config_file. Does it make sense to make it configurable and use it in get_kube_client.
Like the way its done in kubernetes_pod_operator Thanks, Raman Gupta
