[
https://issues.apache.org/jira/browse/AIRFLOW-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029268#comment-17029268
]
ASF subversion and git services commented on AIRFLOW-6678:
----------------------------------------------------------
Commit 96f834389e03884025534fabd862155061f53fd0 in airflow's branch
refs/heads/master from MatthewRBruce
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=96f8343 ]
[AIRFLOW-6678] Pull event logs from Kubernetes (#7292)
Adds an option (defaults to True) to pull and log events from a
Kubernetes pod that fails.
> 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: 1.10.8
>
>
> 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)
