You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/08/04 11:24:00 UTC

[jira] [Commented] (AIRFLOW-3311) Allow Pod Operator to Retain Failed Pods

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

jack commented on AIRFLOW-3311:
-------------------------------

[~ash] This issue is fixed in [https://github.com/apache/airflow/pull/4218]

[https://github.com/apache/airflow/pull/4663]

> Allow Pod Operator to Retain Failed Pods
> ----------------------------------------
>
>                 Key: AIRFLOW-3311
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3311
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: contrib
>    Affects Versions: 2.0.0
>            Reporter: Eamon Keane
>            Assignee: Eamon Keane
>            Priority: Minor
>
> When using the pod operator it is convenient to be able to retain failed pods for log inspectionl
> Airflow 2854 introduced the ability to delete pods made with the pod operator, however it only has configuration to allow you to delete all pods.
> This extends Airflow 2854 to allow the user to specify a flag to keep pods that exit with a non-zero exit code.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)