This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
KubernetesExecutor do not spawn Kubernetes Pod Operator pods. #17629
Labels
affected_version:2.1
Issues Reported for 2.1
affected_version:2.2
Issues Reported for 2.2
area:helm-chart
Airflow Helm Chart
kind:bug
This is a clearly a bug
provider:cncf-kubernetes
Kubernetes provider related issues
Apache Airflow version: 2.1.2 (but happened on 2.0.2 as well)
OS: debian
Apache Airflow Provider versions:
apache-airflow-providers-celery==2.0.0
apache-airflow-providers-cncf-kubernetes==2.0.1
apache-airflow-providers-docker==2.1.0
apache-airflow-providers-elasticsearch==2.0.2
apache-airflow-providers-ftp==2.0.0
apache-airflow-providers-google==5.0.0
apache-airflow-providers-hashicorp==2.0.0
apache-airflow-providers-http==2.0.0
apache-airflow-providers-imap==2.0.0
apache-airflow-providers-mysql==2.1.0
apache-airflow-providers-postgres==2.0.0
apache-airflow-providers-redis==2.0.0
apache-airflow-providers-slack==4.0.0
apache-airflow-providers-sqlite==2.0.0
apache-airflow-providers-ssh==2.1.0
Deployment:
GKE
What happened:
Airflow was working fine, but out of blue, stopped working properly.
Basically, DAG starts and then tasks first task fail, but they were running okay a week ago. KubernetesExecutor stopped spawning KubernetesPodOperators and there are no logs or errors. If I run directly (
kubectl apply -f
) template I use for Operator, it runs successfully.Airflow utilize the same service account for Operator and Executor, so if Executor created successfully, that means no problem with a service account
Also, since DAG syncs successfully, no problem with git-sync.
kubectl get events
does not show any attempts to create any pods for the taskdag_processor_manager.log
also free of any errors.So, Executor successfully created and proceeded to Complete and no Pod Operator was created.
Executor
Pod template
DAG
In scheduler:
Executor logs:
What you expected to happen:
Expect to Executor to create a pod for Kubernetes Pod Operator or throw any type of error.
The text was updated successfully, but these errors were encountered: