[GH-ISSUE #6970] [agent-network] Add agentgateway integration #12285

Open
opened 2026-08-05 01:32:47 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @danehans on GitHub (Jul 29, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/6970

Problem

NetBird Agent Network supports LiteLLM as an AI gateway, but agentgateway currently requires the generic custom-provider path. That misses first-class setup guidance and trusted NetBird user/group attribution in agentgateway policies, limits, and observability.

Proposal

Add agentgateway as a supported AI Gateway integration with LiteLLM-equivalent LLM functionality:

  • Bearer virtual-key authentication, stored and injected by NetBird
  • Anti-spoofed x-netbird-user-id and x-netbird-groups headers
  • OpenAI and Anthropic request-shape detection through the same gateway
  • Catch-all or operator-defined model routing
  • Dashboard copy and standalone/Kubernetes setup documentation

NetBird should remain authoritative for tunnel identity, access policy, model allowlists, and token/spend limits. Agentgateway can provide upstream provider routing, failover, advanced guardrails, and OpenTelemetry-based observability.

Acceptance criteria

  • Add an agentgateway provider catalog entry and dashboard support
  • Support OpenAI Chat Completions, Responses, Embeddings, Anthropic Messages, model listing, and existing SSE streaming behavior
  • Replace client-supplied identity headers with trusted NetBird values
  • Add catalog, synthesizer, routing, anti-spoofing, and end-to-end tests
  • Document agentgateway v1.4+ standalone and Kubernetes configurations
  • Track MCP and A2A integration separately; they are outside the initial LLM provider scope
Originally created by @danehans on GitHub (Jul 29, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/6970 ## Problem NetBird Agent Network supports LiteLLM as an AI gateway, but agentgateway currently requires the generic custom-provider path. That misses first-class setup guidance and trusted NetBird user/group attribution in agentgateway policies, limits, and observability. ## Proposal Add agentgateway as a supported AI Gateway integration with LiteLLM-equivalent LLM functionality: - Bearer virtual-key authentication, stored and injected by NetBird - Anti-spoofed `x-netbird-user-id` and `x-netbird-groups` headers - OpenAI and Anthropic request-shape detection through the same gateway - Catch-all or operator-defined model routing - Dashboard copy and standalone/Kubernetes setup documentation NetBird should remain authoritative for tunnel identity, access policy, model allowlists, and token/spend limits. Agentgateway can provide upstream provider routing, failover, advanced guardrails, and OpenTelemetry-based observability. ## Acceptance criteria - [ ] Add an `agentgateway` provider catalog entry and dashboard support - [ ] Support OpenAI Chat Completions, Responses, Embeddings, Anthropic Messages, model listing, and existing SSE streaming behavior - [ ] Replace client-supplied identity headers with trusted NetBird values - [ ] Add catalog, synthesizer, routing, anti-spoofing, and end-to-end tests - [ ] Document agentgateway v1.4+ standalone and Kubernetes configurations - [ ] Track MCP and A2A integration separately; they are outside the initial LLM provider scope
Author
Owner

@linear-code[bot] commented on GitHub (Jul 29, 2026):

NET-1455

<!-- gh-comment-id:5123471816 --> @linear-code[bot] commented on GitHub (Jul 29, 2026): <!-- linear-linkback --> <p><a href="https://linear.app/netbird/issue/NET-1455">NET-1455</a></p>
Author
Owner

@danehans commented on GitHub (Jul 29, 2026):

/assign

<!-- gh-comment-id:5123498436 --> @danehans commented on GitHub (Jul 29, 2026): /assign
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#12285