Proposals and discussions for the AI Gateway Working Group.
The term AI Gateway in a Kubernetes context refers to a network Gateway (including proxy servers, load-balancers, etc) which (generally) implements the [Gateway API] specification and has capabilities to support networking for AI workloads including AI protocol awareness, [egress gateway] support and [payload processing]. Rather than a distinct product category, it describes infrastructure for enforcing policy on AI traffic, such as token-based rate limiting, fine grained access controls for inference APIs, and payload inspection that enables routing, caching and guardrails.
For more general information about the working group, please see:
- Our README - This provides an overview of the community, contact and communication information.
- Our Charter - This describes what this WG intends to accomplish in detail, our general goals and areas of interest.
As a Kubernetes working group, we do not directly own projects or code, our purpose is to make proposals. As such, this repository is meant for discussions and staging proposals which (generally) will be developed into proposals for specific Kubernetes Special Interest Groups (SIGs) and their sub-projects.
Any code contained in this repo is a prototype only and NOT suitable for anything resembling production
Please see our proposals directory to view the proposals we have so far. If you'd like to submit a new proposal, please contact us in one of our communication channels to get some feedback and identify potential supporters for your proposal in the community who can help move it forward with you.
You are welcome to create and share prototypes for any WG proposal under the prototypes directory
in main branch. This enables collaboration, experimentation, and knowledge sharing across contributors.
However, this Working Group (WG) does not own or maintain production code. All code in this repository is provided strictly for PoC, experimentation, and discussion purposes only. It should not be considered production-ready, officially supported, or suitable for direct reuse in other projects.
More details can be found in the prototypes directory.
Long term, proposals and any mature implementations originating from this WG are expected to move into appropriate Kubernetes subprojects or other relevant upstream repositories, where formal ownership and maintenance can be established.
Our community meetings are held weekly on Thursday 2PM EST (Calendar, Meeting Notes). Convert to your timezone.
You can reach out to members of the community using the following communication channels:
Contributions are readily welcomed!
Learn how to engage with the Kubernetes community on the community page.
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.