Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural logic: KubernetesExecutor runs each task in its own pod. Scheduler creates pod → task runs → pod terminates. Isolation and per-task resource control. DAGs in shared volume or Git-sync. Example: Helm deploys scheduler, workers, webserver; task runs spark-submit in...
Architectural logic: KubernetesExecutor runs each task in its own pod. Scheduler creates pod → task runs → pod terminates. Isolation and per-task resource control. DAGs in shared volume or Git-sync. Example: Helm deploys scheduler, workers, webserver; task runs spark-submit in pod. Best practice: K8sExecutor for isolation; right-size pods; Git-sync; XCom backend; monitor evictions.
Red Flag: LocalExecutor in production for multi-tenant. Pro-Move: 'K8sExecutor; each task gets 4 CPU, 8GB; Git-sync for DAGs—zero shared state, clean isolation.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 2 companies. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.