You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/08/26 05:18: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=17184943#comment-17184943 ]
ASF GitHub Bot commented on AIRFLOW-3311:
-----------------------------------------
bhavaniravi commented on pull request #4160:
URL: https://github.com/apache/airflow/pull/4160#issuecomment-680655869
Any idea why this feature is closed? I would love to have this feature
----------------------------------------------------------------
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
> 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
(v8.3.4#803005)