[jira] [Commented] (AIRFLOW-6678) KubernetesPodOperator logs pod events on failure

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026065#comment-17026065 ] 

ASF GitHub Bot commented on AIRFLOW-6678:
-----------------------------------------

MatthewRBruce commented on pull request #7292: [AIRFLOW-6678] Pull event logs from Kubernetes pod on failure
URL: https://github.com/apache/airflow/pull/7292
 
 
   ---
   Issue link: WILL BE INSERTED BY [boring-cyborg](https://github.com/kaxil/boring-cyborg)
   
   Make sure to mark the boxes below before creating PR: [x]
   
   - [X] Description above provides context of the change
   - [X] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN = JIRA ID<sup>*</sup>
   - [X] Unit tests coverage for changes (not needed for documentation changes)
   - [X] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"
   - [X] Relevant documentation is updated including usage instructions.
   - [X] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   <sup>*</sup> For document-only changes commit message can start with `[AIRFLOW-XXXX]`.
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information.
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


> 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)