|
1 | 1 | # kube-agentic-networking |
2 | 2 |
|
3 | | -Agentic networking policies and governance for agents and tools in Kubernetes |
| 3 | +This subproject aims to deliver the following: |
| 4 | + |
| 5 | +**Core Capabilities** |
| 6 | + |
| 7 | +- Provide standardized APIs for secure, governed communication between agents, tools, and potentially LLMs across Kubernetes cluster boundaries (ingress, egress, and east-west traffic) |
| 8 | + |
| 9 | +- Attempt to design APIs around user-facing goals (e.g., "Agent A can communicate with Tool B") rather than protocol-specific constructs, ensuring adaptability as new AI-first protocols emerge alongside MCP and A2A |
| 10 | + |
| 11 | +- Enable protocol-aware networking capabilities where necessary (e.g., MCP tool-level authorization) while keeping core APIs protocol-agnostic and future-proof |
| 12 | + |
| 13 | +- Establish agent identity and authentication mechanisms that allow agents to be uniquely identified and verified across network boundaries |
| 14 | + |
| 15 | + |
| 16 | +**Security & Governance** |
| 17 | + |
| 18 | +- Define authorization policies that control which agents can communicate with other agents, tools, and LLMs at a granular level (e.g., specific MCP tool functions) |
| 19 | + |
| 20 | +- Integrate AI safety and security extension points to support external authentication, authorization, and policy enforcement decisions |
| 21 | + |
| 22 | +- Provide auditable traffic management capabilities (rate limiting, access controls) suitable for autonomous agent workloads |
| 23 | + |
| 24 | + |
| 25 | +**Ecosystem Integration** |
| 26 | + |
| 27 | +- Maintain alignment and collaboration with Gateway API, Gateway Inference Extension, WG AI Gateway, and WG AI Integration |
| 28 | + |
| 29 | +- Design APIs extensible enough for diverse implementations (service meshes, gateways, future architectures) |
4 | 30 |
|
5 | 31 | ## Community, discussion, contribution, and support |
6 | 32 |
|
|
0 commit comments