
The diagram above describes the three main flows we typically have on an Agentic Application:
- - **The A2A Flow**: Agent 1 sends a request to Kong Agent Gateway, which routes it to Agent 2. Doing so, it enables agent-to-agent coordination and observation.
- - **The MCP Flow**: Agent 2 invokes tools via Kong MCP Route, which routes the requests to existing MCP Servers or RESTful-based Services, enabling standardized tool execution using MCP.
- - **The LLM Flow**: Agent 2 sends LLM requests via Kong LLM Route, which, using the AI Proxy Advanced Plugin configuration, routes the request to external GenAI models (OpenAI, Anthropic).
One of the key benefits is centralized policy enforcement. With Kong, organizations can define authentication, rate limiting, transformation, and security policies once and apply them globally. This ensures that all services, Agents, MCP Servers, and GenAI Models, adhere to the same standards. For example, an enterprise can enforce API key validation, OAuth2 authentication, or JWT verification across all endpoints without requiring individual service teams to implement these controls themselves.
Observability and analytics also play a crucial role. Kong Konnect provides deep insights into traffic patterns, service performance, and usage metrics. For instance, teams can monitor API and AI usage trends, track error rates, and analyze latency distributions across services, all from a centralized dashboard.
VKS implements the Platform layer, which hosts the data plane nodes (Kong Agent Gateway + MCP/LLM Gateway). It also provides an enterprise-grade Kubernetes runtime with networking (Antrea), storage (CSI), and certificate management.
This architecture establishes Kong as the standardized management and traffic governance layer for VKS, helping organizations bridge the gap between traditional infrastructure and AI-native agility. By unifying control across all types of workloads, Kong ensures that organizations can scale confidently without losing visibility or control.
To learn more about how VKS and Kong work together, refer to the full [_Reference Architecture_](https://www.vmware.com/docs/isv-kong-vks?_gl=1*h8gxl5*_ga*NDcxMzI0NTE3LjE3NzczMTQwOTU.*_ga_8VJHMNGE3E*czE3Nzc0NzY1MDUkbzQkZzAkdDE3Nzc0NzY1MDUkajYwJGwwJGgw)_Reference Architecture_.