You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Chris McLennon (Jira)" <ji...@apache.org> on 2020/03/20 16:38:00 UTC

[jira] [Closed] (AIRFLOW-4861) KubernetesPodOperator to print pod event logs when reaching a completion state

     [ https://issues.apache.org/jira/browse/AIRFLOW-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris McLennon closed AIRFLOW-4861.
-----------------------------------
    Resolution: Fixed

> KubernetesPodOperator to print pod event logs when reaching a completion state
> ------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4861
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4861
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>    Affects Versions: 1.10.3
>            Reporter: Chris McLennon
>            Assignee: Chris McLennon
>            Priority: Minor
>
> Currently, when KubernetesPodOperators fail to launch the pod due to an error on the Kubernetes side (e.g. Secret does not exist), it fails the pod and Airflow logs report back that the pod failed to launch without further detail. For Airflow users that do not have Kubernetes access or knowledge, this becomes difficult to debug.
> I'd like to have KubernetesPodOperators print the pod events when the operator reaches a completion state. This will expose any errors on the Kubernetes side before the pod is able to launch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)