hterik opened a new issue, #28186: URL: https://github.com/apache/airflow/issues/28186
### Apache Airflow version 2.5.0 ### What happened 1. Start a task running with KubernetesExecutor 2. Open the **_/rendered-k8s?dag_id=...&task_id=..._** endpoint in the web UI 3. Copy the metadata.name 4. `kubectl logs pod/$name` 5. `Error from server (NotFound): pods "example-sla-dag-sleep-20-1bc7f8d6892849eaac4642c4177e2eab" not found` By inspecting the ### What you think should happen instead Pod name presented in **Rendered K8s Pod Spec** should match the pod name used for running task. Otherwise pod name should not be presented at all. This is not only a problem for users of the UI, also in the code it can be useful to have the real pod-id. I'm in the process of troubleshooting strange errors with task adoption, where there are frequently orphaned tasks found. Currently there appears to be no way to go from TI to pod_id, the adoption-process instead goes the other way, using pod labels to find TIs. So for any TIs that were not found in the adoption, one can not find if they at any point have had matching pods or not. ### How to reproduce _No response_ ### Operating System Ubuntu 22.04 ### Versions of Apache Airflow Providers _No response_ ### Deployment Other Docker-based deployment ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
