good first issuekind:documentationprovider:cncf-kubernetes
倉庫指標
- Star
- (44,809 star)
- PR 合併指標
- (平均合併 7天 18小時) (30 天內合併 834 個 PR)
描述
Apache Airflow version
2.5.0
What happened
- Start a task running with KubernetesExecutor
- Open the /rendered-k8s?dag_id=...&task_id=... endpoint in the web UI
- Copy the metadata.name
kubectl logs pod/$nameError 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
- I agree to follow this project's Code of Conduct