[
https://issues.apache.org/jira/browse/AIRFLOW-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029267#comment-17029267
]
ASF GitHub Bot commented on AIRFLOW-6678:
-----------------------------------------
potiuk commented on pull request #7292: [AIRFLOW-6678] Pull event logs from
Kubernetes pod on failure
URL: https://github.com/apache/airflow/pull/7292
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> KubernetesPodOperator logs pod events on failure
> ------------------------------------------------
>
> Key: AIRFLOW-6678
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6678
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 1.10.7
> Reporter: Matthew Bruce
> Assignee: Matthew Bruce
> Priority: Minor
> Fix For: 2.0.0
>
>
> Currently if a pod fails to launch via a KubernetesPodOperator, the events
> from the pod are not pulled back and logged - i.e. if a pod fails to launch
> because the target image can't be found, or a volume fails to mount the user
> gets no indication of this in the airflow logs.
> There should be an option to pull these events back in the case of a pod
> failure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
