apache/airflow

Support for Kubernetes Executor side task attempt logging for failed tasks in case of task pods doesn't reach running state

Open

#37,435 建立於 2024年2月15日

在 GitHub 查看
 (2 留言) (4 反應) (1 負責人)Python (16,781 fork)batch import
area:providersgood first issuekind:featureprovider:cncf-kubernetes

倉庫指標

Star
 (44,809 star)
PR 合併指標
 (平均合併 7天 18小時) (30 天內合併 834 個 PR)

描述

Description

Right now, when the tasks fail due to pod launch failures or the pod is stuck in the pending phase, then the task logs from the UI are empty. It is very inconvenient for airflow consumers to debug it. They might not have access to the scheduler logs. I believe we can push these failure reasons from the Kubernetes executor to task attempt logs (remote). So, that airflow consumers can able to see task failure reasons from the UI.

Use case/motivation

Right now, when the tasks fail due to pod launch failures or the pod is stuck in the pending phase, then the task logs from the UI are empty. It is very inconvenient for airflow consumers to debug it.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

貢獻者指南