@Marvin how come my flow is marked as "running" and I can see my kubernetes pod up and running but there's simply no logs available and the status is just stuck at "pending" forever?

It seems that there might be a few reasons why your flow is marked as "running" yet presents no logs and is stuck at "pending". Here are a few steps you might consider investigating: 1. Inspect Kubernetes Environment: Ensure the Kubernetes environment is correctly set up and that there are no underlying issues with pod scheduling. You might need to check if there are resource constraints or other limitations affecting your Kubernetes cluster. 2. Logging Configuration: Check if logs are correctly configured in your flow. If logging is not set up, you may not see logs even if the pod is running. The docs on adding logging to flows can help you configure this. 3. Concurrency Limits: There could potentially be concurrency limits or priority issues if you're using work queues or work pools that are causing your flow to wait in pending status. Review your concurrency configurations and priorities as described in the work-pools documentation. Unfortunately, none of these excerpts pinpoint the exact issue, and I don't see a direct answer to why logs are not displaying while a flow is stuck in "pending". If these steps do not resolve the issue, you may need to delve deeper into your specific Kubernetes setup or Prefect configuration. If there’s a known issue related to this scenario, checking Prefect's GitHub issues could be useful. Would you like me to search there for you?

I deployed my flow using

Flow.from_source

and there's usually logs of cloning into the repo, but I don't see any logs