The kubernetes executor is introduced in Apache Airflow 1.10.0. The Kubernetes executor will create a new pod for every task instance.

Example helm charts are available at scripts/ci/kubernetes/kube/{airflow,volumes,postgres}.yaml in the source distribution. The volumes are optional and depend on your configuration. There are two volumes available:

Dags: by storing all the dags onto the persistent disks, all the workers can read the dags from there. Another option is using git-sync, before starting the container, a git pull of the dags repository will be performed and used throughout the lifecycle of the pod.

Logs: by storing the logs onto a persistent disk, all the logs will be available for all the workers and the webserver itself. If you don’t configure this, the logs will be lost after the worker pods shuts down. Another option is to use S3/GCS/etc to store the logs.