seanghaeli opened a new pull request, #75255: URL: https://github.com/apache/airflow/pull/75255
In multi-team mode, the API server reads a running task's live log through the global executor, never the task's team executor. Only the Kubernetes executors (and so `AwsEksExecutor`) fetch live logs through the executor, from the pod, so a team running one with its own namespace or cluster gets "Cannot find pod", or nothing at all when the global executor is a `LocalExecutor`. This resolves the executor the way the scheduler does: the team's own executor, else a global one, cached per team. Finished tasks and other executors aren't affected. Found while testing per-team clusters (#75251) on two real EKS clusters, where each team's live log now comes from its own cluster. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
