Skip to main content

What is KubernetesPodOperator in Airflow

A KubernetesPodOperator is a type of operator in Apache Airflow that allows you to launch a Kubernetes pod as a task in an Airflow workflow. This can be useful if you want to run a containerized workload as part of your pipeline, or if you want to use the power of Kubernetes to manage the resources and scheduling of your tasks.

Here is an example of how you might use a KubernetesPodOperator in an Airflow DAG:

from airflow import DAG
from airflow.operators.kubernetes_pod_operator import KubernetesPodOperator
from airflow.utils.dates import days_ago

default_args = {
    'owner': 'me',
    'start_date': days_ago(2),
}

dag = DAG(
    'kubernetes_sample',
    default_args=default_args,
    schedule_interval=timedelta(minutes=10),
)

# Define a task using a KubernetesPodOperator
task = KubernetesPodOperator(
    namespace='default',
    image="python:3.6-slim",
    cmds=["python", "-c"],
    arguments=["print('hello world')"],
    labels={"foo": "bar"},
    name="test-pod",
    task_id="test-pod",
    is_delete_operator_pod=True,
    dag=dag,
)


In this example, we are defining a task that will launch a Kubernetes pod in the default namespace, using the python:3.6-slim Docker image. The pod will run a single command, print('hello world'), using the python interpreter. The task is given a label of foo: bar and a name of test-pod.

There are many other parameters that you can use to customize the behavior of the KubernetesPodOperator, such as setting resource limits and requests, specifying environment variables, and mounting volumes. You can find a full list of available parameters in the Airflow documentation.

Comments

Post a Comment

Popular posts from this blog

How to migrate the data between AWS and Google Cloud Platform

There are several ways to migrate data between Amazon Web Services (AWS) and Google Cloud Platform (GCP). Here are three common approaches: Use a Cloud Data Integration Tool: Both AWS and GCP offer a range of tools that can help you move data between the two platforms. For example, AWS Data Pipeline is a fully-managed data integration service that can extract data from various sources, transform the data as needed, and load the data into a destination system. On GCP, Cloud Data Fusion is a similar tool that can help you build, execute, and monitor data pipelines between various data sources and destinations. You can use these tools to create a data pipeline that moves data between AWS and GCP. Use a Command-Line Tool: Another option is to use a command-line tool, such as aws s3 cp or gsutil, to transfer data between AWS S3 and GCP Cloud Storage. For example, you can use aws s3 cp to copy data from an S3 bucket to your local machine, and then use gsutil cp to upload the data to Cloud ...
Post a Comment
Read more

Difference between Union and Union All in SQL

You might be using Union or Union All in your SQL code while doing Data Analysis or building Data Pipelines. Ever wondered what is the difference between them and how using one over another can be more efficient? Yes, there is a small yet significant difference between Union and Union All. Let's look at that by understanding each of them individually. 1. Union All  Union All basically allows you to concatenate the table that has a similar structure of tables. The important condition to have Union All of the tables is that both the tables should have the same number of columns. So when you take Union All of two tables what it does in the background is it directly joins the tables without removing duplicates or redundant records.   2. Union  Union is also similar to Union All except one difference that it removes the duplicates records before taking the Union of the tables.  There is one disadvantage of Union over Union All, that since it removes duplicated records bef...
Post a Comment
Read more

What is Shuffling in Spark

Shuffling in Spark is a mechanism that Re-Distributes the data across different executors or workers in the clusters.  Why do we need to Re-Distribute the data?    A) Re-Distribution is needed when there is a need of increasing or decreasing the data partitions in the situations below: When the partitions are not sufficient enough to process the data load in the cluster When the partitions are too high in numbers that it creates task scheduling overhead and it becomes the bottleneck in the processing time. Re-Distribution can also be achieved by executing the shuffling on existing distributed data collection like RDD, DataFrames, etc by using the "Repartition" and "Coalesce" APIs in Spark. B) During Aggregation and Joins on data collection in Spark, all the data records belonging to aggregation or join should reside in the single partition and when the existing partitioning scheme doesn't satisfy this condition there is a need to re-distributing the data in in...
Post a Comment
Read more