Kubernetes executor for dynamic scaling in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does the Kubernetes Executor scale Airflow tasks?

In Airflow's Kubernetes Executor, how does dynamic scaling of task pods happen?

A It creates a new pod for each task dynamically and deletes it after task completion.

B It pre-creates a fixed number of pods and reuses them for all tasks.

C It runs all tasks inside a single pod and scales the pod's CPU resources.

D It schedules tasks on existing Kubernetes nodes without creating pods.

💡 Hint

Think about how Kubernetes manages workloads with pods for isolation.

The Kubernetes Executor creates a separate pod for each task dynamically. This allows Airflow to scale tasks independently and clean up resources after task completion.

💻 Command Output

intermediate

Output of kubectl get pods during Airflow task execution

What is the expected output of kubectl get pods when Airflow is running tasks with the Kubernetes Executor?

Apache Airflow

kubectl get pods

A Only one pod named airflow-scheduler running all tasks

B Multiple pods named airflow-task-xxxx in Running or Completed state

C No pods related to Airflow tasks, only system pods

D Pods named airflow-webserver running tasks

💡 Hint

Remember each task runs in its own pod with Kubernetes Executor.

With Kubernetes Executor, each Airflow task runs in its own pod. So kubectl get pods shows multiple pods named like airflow-task-xxxx in Running or Completed states.

❓ Configuration

advanced

Configuring Airflow to use Kubernetes Executor with dynamic scaling

Which configuration snippet correctly enables the Kubernetes Executor with dynamic pod scaling in airflow.cfg?

A

[core]
executor = KubernetesExecutor

[kubernetes]
namespace = airflow
in_cluster = True
worker_container_repository = apache/airflow
worker_container_tag = 2.6.2

B

[core]
executor = LocalExecutor

[kubernetes]
namespace = airflow
in_cluster = False

C

[core]
executor = CeleryExecutor

[kubernetes]
namespace = default
in_cluster = True

D

[core]
executor = KubernetesExecutor

[kubernetes]
namespace = default
in_cluster = False
worker_container_repository = apache/airflow

💡 Hint

Check the executor type and Kubernetes section for correct settings.

To enable Kubernetes Executor with dynamic scaling, set executor = KubernetesExecutor under [core] and configure the Kubernetes section with namespace, in_cluster, and worker container details.

❓ Troubleshoot

advanced

Troubleshooting Airflow task pods stuck in Pending state

You notice Airflow task pods created by Kubernetes Executor remain in Pending state and never run. What is the most likely cause?

A The Airflow webserver is not reachable by the user.

B Airflow scheduler is down and not creating pods.

C Insufficient Kubernetes cluster resources or missing node selectors preventing pod scheduling.

D The DAG files are missing from the Airflow home directory.

💡 Hint

Think about what causes pods to stay Pending in Kubernetes.

Pods stay in Pending state if Kubernetes cannot find suitable nodes to schedule them. This often happens due to insufficient cluster resources or restrictive node selectors.

🔀 Workflow

expert

Order the steps for Airflow Kubernetes Executor dynamic scaling

Arrange the following steps in the correct order for how Airflow Kubernetes Executor dynamically scales task execution.

A 3,2,1,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about the natural flow from scheduler to pod creation to execution.

The scheduler first detects the task, then creates the pod manifest, Kubernetes schedules the pod, and finally the task runs inside the pod.

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