Kubernetes executor for dynamic scaling in Apache Airflow - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Kubernetes Executor in Apache Airflow?

The Kubernetes Executor allows Airflow to run each task in its own Kubernetes pod, enabling dynamic scaling and isolation of tasks.

beginner

How does dynamic scaling work with the Kubernetes Executor?

Dynamic scaling means Airflow creates and deletes pods on demand based on the number of tasks to run, so resources are used efficiently.

beginner

Which Airflow configuration file is used to enable the Kubernetes Executor?

The airflow.cfg file is used to set the executor to KubernetesExecutor by changing the 'executor' parameter.

intermediate

What is the role of the Kubernetes pod template in the Kubernetes Executor?

The pod template defines how each task pod is created, including resources, environment variables, and volumes.

intermediate

Why is using the Kubernetes Executor beneficial for resource management?

It allows Airflow to use cluster resources only when needed, reducing idle resource waste and improving cost efficiency.

What does the Kubernetes Executor do in Airflow?

A Runs all tasks in a single pod

B Runs each task in a separate Kubernetes pod

C Runs tasks only on the Airflow scheduler node

D Runs tasks on virtual machines only

The Kubernetes Executor runs each task in its own pod, enabling dynamic scaling.

Which file do you edit to switch Airflow to use the Kubernetes Executor?

A airflow.cfg

B kubeconfig.yaml

C Dockerfile

D requirements.txt

The airflow.cfg file contains the executor setting to enable Kubernetes Executor.

What triggers Airflow to create new pods when using the Kubernetes Executor?

A Manual pod creation

B CPU usage on the scheduler

C Number of tasks to run

D Fixed number of pods at startup

Pods are created dynamically based on how many tasks need to run.

What is a key benefit of dynamic scaling with Kubernetes Executor?

A Efficient use of cluster resources

B Tasks run slower

C Requires manual pod management

D Uses fixed resources regardless of workload

Dynamic scaling helps use resources only when needed, saving costs.

What does the pod template specify in Kubernetes Executor?

A Scheduler settings

B Airflow DAG definitions

C Database connection info

D Pod configuration like resources and environment

The pod template defines how task pods are created and configured.

Explain how the Kubernetes Executor enables dynamic scaling in Airflow.

Think about how tasks and pods relate and how resources are managed.

Describe the role of the pod template in the Kubernetes Executor setup.

Consider what details are needed to create a pod for a task.

Practice

1. What is the main benefit of using the Kubernetes executor in Airflow?

easy

A. It disables task retries to save resources.

B. It stores all task logs in a local file system.

C. It schedules tasks only on a single fixed server.

D. It runs each task in its own pod, allowing dynamic scaling.

Solution

1. Step 1: Understand Kubernetes executor behavior

   The Kubernetes executor runs each Airflow task in a separate pod, which allows tasks to run independently and scale dynamically.

2. Step 2: Compare options with executor features

   Options B, C, and D describe behaviors not related to Kubernetes executor's main feature of dynamic pod creation and scaling.

3. Final Answer:

   It runs each task in its own pod, allowing dynamic scaling. -> Option D

4. Quick Check:

   Kubernetes executor = dynamic pod scaling [OK]

Hint: Kubernetes executor = one pod per task for scaling [OK]

Common Mistakes:

• Thinking tasks run on a single server
• Confusing executor with local logging
• Assuming retries are disabled

2. Which configuration key is required to enable the Kubernetes executor in Airflow's airflow.cfg?

easy

A. executor = LocalExecutor

B. executor = CeleryExecutor

C. executor = KubernetesExecutor

D. executor = SequentialExecutor

Solution

1. Step 1: Identify executor configuration key

   In airflow.cfg, the executor key sets which executor Airflow uses.

2. Step 2: Match correct executor name for Kubernetes

   The correct value to enable Kubernetes executor is KubernetesExecutor. Other options are different executors.

3. Final Answer:

   executor = KubernetesExecutor -> Option C

4. Quick Check:

   Enable Kubernetes executor = executor = KubernetesExecutor [OK]

Hint: Set executor = KubernetesExecutor in airflow.cfg [OK]

Common Mistakes:

• Using LocalExecutor or CeleryExecutor by mistake
• Misspelling KubernetesExecutor
• Changing unrelated config keys

3. Given this Airflow task using Kubernetes executor, what happens when the DAG runs?

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime
with DAG('example', start_date=datetime(2024,1,1)) as dag:
    task = BashOperator(task_id='print_date', bash_command='date')

medium

A. The task runs inside a new Kubernetes pod created dynamically.

B. The task runs on the Airflow scheduler machine only.

C. The task fails because BashOperator is not supported with Kubernetes executor.

D. The task runs on a fixed worker node without pod creation.

Solution

1. Step 1: Understand task execution with Kubernetes executor

   When using Kubernetes executor, each task runs inside its own pod created dynamically in the Kubernetes cluster.

2. Step 2: Analyze the given BashOperator task

   The BashOperator runs a simple shell command. With Kubernetes executor, this command runs inside a new pod, not on the scheduler or fixed node.

3. Final Answer:

   The task runs inside a new Kubernetes pod created dynamically. -> Option A

4. Quick Check:

   BashOperator + Kubernetes executor = dynamic pod run [OK]

Hint: Kubernetes executor runs each task in a new pod [OK]

Common Mistakes:

• Assuming tasks run on scheduler machine
• Thinking BashOperator is unsupported
• Believing pods are not created dynamically

4. You configured Airflow with Kubernetes executor but tasks are not running and pods are not created. What is the most likely cause?

medium

A. The Kubernetes cluster credentials are missing or incorrect.

B. The DAG file has syntax errors unrelated to executor.

C. The Airflow scheduler is running with LocalExecutor.

D. The BashOperator command is invalid.

Solution

1. Step 1: Check Kubernetes executor requirements

   Kubernetes executor needs valid cluster credentials to create pods dynamically.

2. Step 2: Identify why pods are not created

   If no pods appear, missing or wrong Kubernetes credentials is the most common cause, blocking pod creation.

3. Final Answer:

   The Kubernetes cluster credentials are missing or incorrect. -> Option A

4. Quick Check:

   No pods + Kubernetes executor = check cluster credentials [OK]

Hint: No pods? Verify Kubernetes credentials first [OK]

Common Mistakes:

• Blaming DAG syntax errors
• Assuming scheduler executor type is unrelated
• Thinking BashOperator command causes pod creation failure

5. You want to optimize Airflow with Kubernetes executor to handle many short tasks efficiently. Which approach helps reduce pod startup overhead?

hard

A. Increase task retries to avoid pod creation failures.

B. Use pod templates with pre-configured settings and enable pod reuse.

C. Disable Kubernetes executor and switch to SequentialExecutor.

D. Run all tasks in a single pod to save resources.

Solution

1. Step 1: Understand pod startup overhead in Kubernetes executor

   Each pod creation takes time, so reducing overhead improves efficiency for many short tasks.

2. Step 2: Identify optimization methods

   Using pod templates with pre-set configs and enabling pod reuse reduces startup time and resource use.

3. Step 3: Evaluate other options

   Disabling Kubernetes executor or running all tasks in one pod loses scaling benefits. Increasing retries does not reduce pod startup time.

4. Final Answer:

   Use pod templates with pre-configured settings and enable pod reuse. -> Option B

5. Quick Check:

   Pod reuse + templates = faster task startup [OK]

Hint: Use pod templates and reuse to speed up pods [OK]

Common Mistakes:

• Switching to SequentialExecutor loses scaling
• Running all tasks in one pod breaks isolation
• Increasing retries does not reduce pod startup