ketozhang commented on issue #36077: URL: https://github.com/apache/airflow/issues/36077#issuecomment-1842042063
Related closed issue with a vague scope https://github.com/apache/airflow/issues/10861 --- The logging all events as ERROR still exists in main. https://github.com/apache/airflow/blob/ace97c0f0b64bd003bafa50e02cdfc10a8303936/airflow/providers/cncf/kubernetes/operators/pod.py#L780-L785 --- Understandably, Kubernetes does not isolate stdout from stderr in its container log API, which is why KPO was implemented to container logs to INFO. The options I can think of is make this function aware of the container status (beyond just running) https://github.com/apache/airflow/blob/ace97c0f0b64bd003bafa50e02cdfc10a8303936/airflow/providers/cncf/kubernetes/utils/pod_manager.py#L398-L473 or give the user an ability to write stderr (or anything) to `/dev/termination-log` for KPO (same can be done on @task.kubernetes with the task logger) https://kubernetes.io/docs/tasks/debug/debug-application/determine-reason-pod-failure/ This seems last part seems out of the scope. I can make another ticket if interested. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
