We use a fork of the KubernetesPodOperator in house (and we don't use the
Executor). The steps to use it are roughly:
1) Set up your Kubernetes cluster (can be EKS, GKE, etc.)
2) Make sure your Airflow cluster has network access to the Kubernetes API
servers
3) Create a ServiceAccount for the Airf
Thanks, James and Kamil! Please let me know if you have any examples of
setting up Kubernetes Executor and Operator.
On Tue, Apr 9, 2019 at 8:03 AM James Meickle
wrote:
> Yes, that summary is correct - the Executor is using Kubernetes to execute
> all Airflow tasks (each wrapped by a temporary A
Yes, that summary is correct - the Executor is using Kubernetes to execute
all Airflow tasks (each wrapped by a temporary Airflow process), while the
PodOperator is using Kubernetes only for that task, to execute one Pod
(which likely won't run any Airflow code at all).
On Tue, Apr 9, 2019 at 3:17
Hi Ashwin,
I had exactly same question couple of days ago. Let me try to explain. If
I'm wrong please someone correct me.
Kubernetes Executor is used to execute TaskInstance, which means that Pod
is created of that TaskInstance that for ex. could be BashOperator or
SlackAPIOperator and after exec
Hi Airflow users,
What is the difference between Kube executor vs pod operator?
http://airflow.apache.org/kubernetes.html
Thanks,
Ash
