don't forget that agent is a lightweight process rather than an entire execution layer
I believe the reason for that is more related to Kubernetes permissions rather than Prefect agent limitations - it would be difficult to deploy flow run pods from a process running in one Kubernetes namespace to the other namespace because this process has by default no access to that other Kubernetes namespace
(I'm no Kubernetes admin though - you may ask on Kubernetes discourse to be sure)
2 months ago
Okay. We thought the overhead of monitoring and deploying a separate agent is still considerably high, hence the question. I‘m also not sure at all about the Kubernetes rights, however would have thought that with the right service account it should be possible.