Using Airflow Providers With KubernetesPodOperator
PreviousAirflow Operators - A ComparisonNextCan Next Scheduled Run Automatically Re-Run failed Task?
Last updated
Last updated
When you're constrained to use KubernetesPodOperator you will be at a disadvantage of using Airflow providers. There is something you can do about it. Using Airflow provider like any other library.
Install airflow and associated providers you need in the Docker image, KubernetesPodOperator will be using.
Create a python script that will be consumed by KubernetesPodOperator
Inside the script, import the provider operator and call its execute method