GitHub user JMRaczynski edited a discussion: Should running KubernetesPodOperator pods terminate on Airflow scheduler restart?
Question as in title. For `KubernetesExecutor`, it is explicitly stated in [docs](https://airflow.apache.org/docs/apache-airflow-providers-cncf-kubernetes/stable/kubernetes_executor.html#but-what-about-cases-where-the-scheduler-pod-crashes) that scheduler crashes don't lead to task failures/re-runs. I can't find similar information about `KubernetesPodOperator`. I currently use Airflow 3.1.3 with `apache-airflow-providers-cncf-kubernetes` 10.9.0 and `LocalExecutor`. On scheduler restart I see that currently running KPO pods are terminated and then recreated after scheduler restart. I do not set `reattach_on_restart` parameter in my KPOs, so I expect it to be set to default value `True`. Is it an expected behavior or a bug? If it is expected, is it possible to prevent KPO pods in the running state from termination on scheduler restart (without hacks like custom `on_kill()` implementation? GitHub link: https://github.com/apache/airflow/discussions/61734 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
