Runner

Deploys an Agno agent or team as a Kubernetes Deployment with a Service, providing a REST API endpoint.

​

agno/runner

​

Config

​

Outputs

​

Dependencies

• agno/agent or agno/team (exactly one required) — the agent or team to deploy
• gcp/gke (required) — Kubernetes cluster for deployment

​

Example — Deploy an agent

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

​

Example — Deploy a team with authentication

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

​

Authentication

​

Notes

• You must provide exactly one of agent or team.
• The cluster and namespace fields are immutable — changing them requires deleting and recreating the runner.
• The runner creates a Kubernetes Deployment and Service as child resources. These are automatically managed.
• 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 agent/team spec as environment variables and reconstructs it at startup.
• The runner includes health checks (startup, liveness, readiness probes) on /health.