How to Orchestrate Multi-Agent Workflows on Kubernetes with Agentspan
Blog post from Orkes
Agentspan is presented as an orchestration layer that turns AI agent definitions into durable server-side workflows, separating the lifecycle of deployment, worker serving, and execution to support scalable multi-agent systems. The walkthrough deploys Agentspan’s control plane, PostgreSQL database, credentials, and networking on Kubernetes through Helm, optionally using K3D for local testing, then connects a Python SDK to the port-forwarded service. It builds a company-research team in which a coordinator uses handoff to trigger a deep-analysis agent, which runs market and risk specialists in parallel through separate Python tools. The team is registered once with `runtime.deploy`, its tool workers remain active in a separate process through `runtime.serve`, and later requests invoke the registered workflow by name with `runtime.run`. Completed executions can be examined through the API and UI, where the coordinator and nested agents appear as distinct executions and timelines reveal handoffs and parallel work. The central operating model is that Kubernetes manages the control plane, agent definitions can fit CI/CD workflows, workers can scale independently, and execution history supports debugging and observability.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 14 | 2,407 | 415 | 121 | -3% |
| Multi-agent systems | 6 | 536 | 207 | 77 | -27% |
| Secrets Management | 5 | 1,971 | 393 | 127 | +1% |
| LLM | 2 | 6,889 | 1,263 | 265 | -9% |
| Observability | 2 | 4,900 | 921 | 200 | +5% |
| AI Agents | 1 | 5,835 | 1,407 | 272 | -21% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.