Implementations¶
This page lists implementations of the Kube Agentic Networking APIs and their conformance status. It follows the same model as the Gateway API implementations page.
An implementation is listed as conformant when it has submitted a passing conformance report for at least one profile. Reports are the source of truth: each entry below links to the implementation's submitted reports in the repository.
Note
The APIs are still experimental (XAccessPolicy is v1alpha1, XBackend
is v0alpha0) and may change between releases. Conformance claims are made
against a specific extension version.
Conformant Implementations¶
| Implementation | Organization | Profile | Extended Features | Reports |
|---|---|---|---|---|
| Kube Agentic Networking reference implementation | Kubernetes SIG Network | Gateway | SPIFFE source matching, External auth | Reports |
Kube Agentic Networking reference implementation¶
The reference implementation is an Envoy-based Gateway API controller
maintained in this repository. It implements the full Gateway conformance
profile, including MCP tool-level authorization, CEL-based rules, SPIFFE/mTLS
agent identity, external authorization, and authorization tracing.
Adding your implementation¶
If you implement the Kube Agentic Networking APIs, we would love to list you here. To be added:
- Run the conformance suite against your implementation.
- Generate and submit a conformance report by following the submission process.
- In the same or a follow-up Pull Request, add your implementation to the table on this page with a short description.
If your implementation is still working toward conformance, reach out in the #sig-network-agentic-networking Slack channel — we can help you get there.