@Marvin with a prefect kubernetes deployment, is it always a 1-1 relationships between flow runs and job pods?

It appears from the Prefect documentation on Kubernetes deployment that each flow run in a Kubernetes deployment is configured to create a corresponding job within the Kubernetes namespace you specify. The documentation does not explicitly state a 1-1 relationship between flow runs and job pods, but it is implied that a job is created for each flow run as part of its execution environment. There might be additional settings related to job management, like image pull policy or configuration of pod creation timeout, but the basic premise points towards each flow run corresponding to a Kubernetes job, which typically runs in its own pod. For completeness, let's check for GitHub issues that might address this specific question. There doesn't appear to be any GitHub issues that specifically address the relationship between flow runs and job pods in a Kubernetes deployment for Prefect. However, based on the documentation, it seems that the relationship is indeed typically 1-1, with a Kubernetes job created for each flow run. If you need a more definitive or nuanced answer, I would suggest consulting Prefect community channels or reaching out directly to Prefect support.