Unfortunately, there seems to be no direct documentation about issues with retrieving all Kubernetes pod logs or displaying them fully in the Prefect UI. However, based on the search results, including GitHub issues, it's not uncommon to encounter various issues related to Prefect's interaction with Kubernetes. Issues mentioned range from incorrect flow state reporting and QueuePool issues with large numbers of tasks, to flow on_crashed/on_cancellation hooks not executing correctly with KubernetesWorker. If you are having specific problems with logs not being fully displayed or captured in the Prefect UI, it could be related to those broader integration issues. Depending on how your Prefect agents and flows are set up, it might be worth checking the Prefect server logs or agent logs, which could provide more insight into why the logs are not being fully captured or displayed. For more detailed information and guidance, I suggest checking the following resources: 1. How Prefect works with Kubernetes (although this may not be directly related to logs). 2. Visiting the GitHub Issues for Prefect might provide insights or help identify similar problems: - Issue related to Flows with subflows incorrectly reporting state as Failed - Issue related to Database QueuePool issue with 1500+ task flows - Issue related to Flow hooks `on_crashed` / `on_cancellation` not executing correctly with KubernetesWorker Please note that while these issues do not solve your query directly, they indicate that running complex workflows in Kubernetes with Prefect might involve intricate problems affecting various aspects, such as logs. If you can't find a solution in the documentation or issues, consider reaching out through community channels or opening a new GitHub issue with full details of your problem.