GitHub user potiuk added a comment to the discussion: Unexpected SIGTERM on Tasks (Airflow 2.10.5 on GKE with KubernetesExecutor and No Resource Constraints)
I think your best bet is to attempt to upgrade to Airflow 3. This is issue might take forever to diagnose because there is absolutely no clue on why it happens. The whole mechanism of heartbeating, supervising running tasks, etc. that could be causeing it had been completely rewritten there and I think the fastest way to get this problem solved is to simply switch to Airflow 3. GitHub link: https://github.com/apache/airflow/discussions/62978#discussioncomment-16018977 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
