Runner

Deploys one or more Agno agents and teams as a Kubernetes Deployment with a Service, providing a REST API endpoint.

​

agno/runner

​

Config

​

Outputs

​

Dependencies

• agno/agent and/or agno/team (at least one required) — the agents and teams to deploy
• kubernetes/config (required) — access to the target cluster
• kubernetes/namespace (required) — namespace for the runner

​

Example — Deploy an agent

provider: agno
resource: runner
name: my-agent
config:
  agents:
    - provider: agno
      resource: agent
      name: assistant
  config:
    provider: kubernetes
    resource: config
    name: my-cluster
  namespace:
    provider: kubernetes
    resource: namespace
    name: agents
  replicas: 2
  public: false
  cpu: "500m"
  memory: "2Gi"

​

Example — Deploy a team with authentication

provider: agno
resource: runner
name: research-team
config:
  teams:
    - provider: agno
      resource: team
      name: research-team
  config:
    provider: kubernetes
    resource: config
    name: my-cluster
  namespace:
    provider: kubernetes
    resource: namespace
    name: agents
  security_key: "my-secret-key"
  public: true

​

Authentication

​

Notes

• Provide at least one entry in agents or teams. Agent names must be unique within agents, and team names unique within teams.
• The config and namespace fields are immutable — changing them requires deleting and recreating the runner.
• The runner creates a Kubernetes Deployment and Service named agno-<name>. These are automatically managed.
• Create and update wait until the Deployment’s replicas are ready.
• When public: true, a LoadBalancer Service is created, providing an external IP. Otherwise, the service is only accessible within the cluster.
• The container receives the combined agent and team specs and reconstructs every agent and team at startup.
• The runner includes health checks (startup, liveness, readiness probes) on /health.