Javier162380 opened a new issue #10861: URL: https://github.com/apache/airflow/issues/10861
<!-- Welcome to Apache Airflow! For a smooth issue process, try to answer the following questions. Don't worry if they're not all applicable; just try to include what you can :-) If you need to include code snippets or logs, please put them in fenced code blocks. If they're super-long, please use the details tag like <details><summary>super-long log</summary> lots of stuff </details> Please delete these comment blocks before submitting the issue. --> **Description** <!-- A short description of your feature --> Currently, the Kubernetes Pod Operator Airflow raised an error message when the status of the pod launch is different from success https://github.com/apache/airflow/blob/ff7232761497985720387c4288439ac1dce2ee77/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py#L303. It is not really descriptive when this failure is not due to an exception based on the task and it is regarding an external factor. For instance, the Kubernetes task gets out of resources, it will be ideal on all these cases return along with the state of the Kubernetes pod the reason according to the Kubernetes API of why this pod get this issue and retrieve this reasons as part of the error message. I think it could make the developer debugger experience much nicer. I think is some sort of event logging in the code https://github.com/apache/airflow/blob/ff7232761497985720387c4288439ac1dce2ee77/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py#L447 but I never get this kind of error **Use case / motivation** <!-- What do you want to happen? Rather than telling us how you might implement this solution, try to take a step back and describe what you are trying to achieve. --> **Related Issues** <!-- Is there currently another issue associated with this? --> ---------------------------------------------------------------- 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: [email protected]
