Skip to content

Commit 9e5df55

Browse files
shaneuttshaneutt
committed
add WG AI Gateway
Signed-off-by: Shane Utt <[email protected]>
1 parent 8a9b69f commit 9e5df55

File tree

7 files changed

+200
-0
lines changed

7 files changed

+200
-0
lines changed

‎OWNERS_ALIASES

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,13 @@ aliases:
130130
- mfahlandt
131131
- ritazh
132132
- terrytangyuan
133+
wg-ai-gateway-leads:
134+
- keithmattix
135+
- kflynn
136+
- kfswain
137+
- nirrozenbaum
138+
- shaneutt
139+
- xunzhuo
133140
wg-ai-integration-leads:
134141
- ardaguclu
135142
- rushmash91

‎sig-list.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
6262
| Name | Label | Stakeholder SIGs |Organizers | Contact | Meetings |
6363
|------|-------|------------------|-----------|---------|----------|
6464
|[AI Conformance](wg-ai-conformance/README.md)|[ai-conformance](https://github.com/kubernetes/kubernetes/labels/wg%2Fai-conformance)|* Architecture<br>* Testing<br>|* [Janet Kuo](https://github.com/janetkuo), Google<br>* [Mario Fahlandt](https://github.com/mfahlandt), Kubermatic GmbH<br>* [Rita Zhang](https://github.com/ritazh), Microsoft<br>* [Yuan Tang](https://github.com/terrytangyuan), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-ai-conformance)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-ai-conformance)|* Regular WG Meeting: [Thursdays at 10:00 PT (Pacific Time) (weekly)]()<br>
65+
|[AI Gateway](wg-ai-gateway/README.md)|[ai-gateway](https://github.com/kubernetes/kubernetes/labels/wg%2Fai-gateway)|* Network<br>|* [Keith Mattix](https://github.com/keithmattix), Microsoft<br>* [Flynn](https://github.com/kflynn), Buoyant<br>* [Kellen Swain](https://github.com/kfswain), Google<br>* [Nir Rozenbaum](https://github.com/nirrozenbaum), IBM<br>* [Shane Utt](https://github.com/shaneutt), Red Hat<br>* [Xunzhuo](https://github.com/xunzhuo), Tencent<br>|* [Slack](https://kubernetes.slack.com/messages/wg-ai-gateway)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-ai-gateway)|* WG AI Gateway Bi-Weekly Meeting (Earlier Option): [Mondays at 12PM UTC (bi-weekly)]()<br>* WG AI Gateway Bi-Weekly Meeting (Later Option): [Thursdays at 6PM UTC (bi-weekly)]()<br>
6566
|[AI Integration](wg-ai-integration/README.md)|[ai-integration](https://github.com/kubernetes/kubernetes/labels/wg%2Fai-integration)|* API Machinery<br>* Apps<br>* Architecture<br>* Auth<br>* CLI<br>|* [Arda Guclu](https://github.com/ardaguclu), Red Hat<br>* [Arush Sharma](https://github.com/rushmash91), Amazon<br>* [Zvonko Kaiser](https://github.com/zvonkok), NVIDIA<br>|* [Slack](https://kubernetes.slack.com/messages/wg-ai-integration)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-ai-integration)|* WG AI Integration Weekly Meeting: [Wednesdays at 9:30 PT (Pacific Time) (weekly)]()<br>
6667
|[Batch](wg-batch/README.md)|[batch](https://github.com/kubernetes/kubernetes/labels/wg%2Fbatch)|* Apps<br>* Autoscaling<br>* Node<br>* Scheduling<br>|* [Kevin Hannon](https://github.com/kannon92), Red Hat<br>* [Marcin Wielgus](https://github.com/mwielgus), Google<br>* [Maciej Szulik](https://github.com/soltysh), Defense Unicorns<br>* [Swati Sehgal](https://github.com/swatisehgal), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-batch)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-batch)|* Regular Meeting ([calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com)): [Thursdays (starting February 15th 2024)s at 3PM CET (Central European Time) (monthly)](https://zoom.us/j/98329676612?pwd=c0N2bVV1aTh2VzltckdXSitaZXBKQT09)<br>
6768
|[Data Protection](wg-data-protection/README.md)|[data-protection](https://github.com/kubernetes/kubernetes/labels/wg%2Fdata-protection)|* Apps<br>* Storage<br>|* [Xing Yang](https://github.com/xing-yang), VMware<br>* [Xiangqian Yu](https://github.com/yuxiangqian), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-data-protection)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-data-protection)|* Regular WG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/6933410772)<br>

‎sig-network/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
7373
## Working Groups
7474

7575
The following [working groups][working-group-definition] are sponsored by sig-network:
76+
* [WG AI Gateway](/wg-ai-gateway)
7677
* [WG Device Management](/wg-device-management)
7778
* [WG Node Lifecycle](/wg-node-lifecycle)
7879
* [WG Serving](/wg-serving)

‎sigs.yaml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3575,6 +3575,57 @@ workinggroups:
35753575
liaison:
35763576
github: pohly
35773577
name: Patrick Ohly
3578+
- dir: wg-ai-gateway
3579+
name: AI Gateway
3580+
mission_statement: >
3581+
The AI Gateway Working Group focuses on the intersection of AI and networking,
3582+
particularly in the context of extending load-balancer, gateway and proxy technologies
3583+
to manage and route traffic for AI Inference.
3584+
3585+
charter_link: charter.md
3586+
stakeholder_sigs:
3587+
- Network
3588+
label: ai-gateway
3589+
leadership:
3590+
chairs:
3591+
- github: keithmattix
3592+
name: Keith Mattix
3593+
company: Microsoft
3594+
email: [email protected]
3595+
- github: kflynn
3596+
name: Flynn
3597+
company: Buoyant
3598+
email: [email protected]
3599+
- github: kfswain
3600+
name: Kellen Swain
3601+
company: Google
3602+
email: [email protected]
3603+
- github: nirrozenbaum
3604+
name: Nir Rozenbaum
3605+
company: IBM
3606+
email: [email protected]
3607+
- github: shaneutt
3608+
name: Shane Utt
3609+
company: Red Hat
3610+
email: [email protected]
3611+
- github: xunzhuo
3612+
name: Xunzhuo
3613+
company: Tencent
3614+
email: [email protected]
3615+
meetings:
3616+
- description: WG AI Gateway Bi-Weekly Meeting (Earlier Option)
3617+
day: Monday
3618+
time: 12PM
3619+
tz: UTC
3620+
frequency: bi-weekly
3621+
- description: WG AI Gateway Bi-Weekly Meeting (Later Option)
3622+
day: Thursday
3623+
time: 6PM
3624+
tz: UTC
3625+
frequency: bi-weekly
3626+
contact:
3627+
slack: wg-ai-gateway
3628+
mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-ai-gateway
35783629
- dir: wg-ai-integration
35793630
name: AI Integration
35803631
mission_statement: >

‎wg-ai-gateway/OWNERS

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# See the OWNERS docs at https://go.k8s.io/owners
2+
3+
reviewers:
4+
- wg-ai-gateway-leads
5+
approvers:
6+
- wg-ai-gateway-leads
7+
labels:
8+
- wg/ai-gateway

‎wg-ai-gateway/README.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
<!---
2+
This is an autogenerated file!
3+
4+
Please do not edit this file directly, but instead make changes to the
5+
sigs.yaml file in the project root.
6+
7+
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
8+
--->
9+
# AI Gateway Working Group
10+
11+
The AI Gateway Working Group focuses on the intersection of AI and networking, particularly in the context of extending load-balancer, gateway and proxy technologies to manage and route traffic for AI Inference.
12+
13+
The [charter](charter.md) defines the scope and governance of the AI Gateway Working Group.
14+
15+
## Stakeholder SIGs
16+
* [SIG Network](/sig-network)
17+
18+
## Meetings
19+
*Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-gateway) for the group will typically add invites for the following meetings to your calendar.*
20+
* WG AI Gateway Bi-Weekly Meeting (Earlier Option): [Mondays at 12PM UTC]() (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=12PM&tz=UTC).
21+
* WG AI Gateway Bi-Weekly Meeting (Later Option): [Thursdays at 6PM UTC]() (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=6PM&tz=UTC).
22+
23+
## Organizers
24+
25+
* Keith Mattix (**[@keithmattix](https://github.com/keithmattix)**), Microsoft
26+
* Flynn (**[@kflynn](https://github.com/kflynn)**), Buoyant
27+
* Kellen Swain (**[@kfswain](https://github.com/kfswain)**), Google
28+
* Nir Rozenbaum (**[@nirrozenbaum](https://github.com/nirrozenbaum)**), IBM
29+
* Shane Utt (**[@shaneutt](https://github.com/shaneutt)**), Red Hat
30+
* Xunzhuo (**[@xunzhuo](https://github.com/xunzhuo)**), Tencent
31+
32+
## Contact
33+
- Slack: [#wg-ai-gateway](https://kubernetes.slack.com/messages/wg-ai-gateway)
34+
- [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-gateway)
35+
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fai-gateway)
36+
<!-- BEGIN CUSTOM CONTENT -->
37+
38+
<!-- END CUSTOM CONTENT -->

‎wg-ai-gateway/charter.md

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
# WG AI Gateway Charter
2+
3+
This charter adheres to the conventions described in the [Kubernetes Charter
4+
README] and uses the Roles and Organization Management outlined in
5+
[wg-governance].
6+
7+
[wg-governance]:https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
8+
[Kubernetes Charter README]:https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
9+
10+
## Scope
11+
12+
The AI Gateway Working Group focuses on the intersection of AI and
13+
networking, particularly in the context of extending load-balancer, gateway
14+
and proxy technologies to manage and route traffic for AI Inference.
15+
16+
This working group will define terms like "AI Gateway" within the context of
17+
Kubernetes and key use cases for users and implementations. It will propose
18+
deliverables that need to be adopted in order to serve AI Inference on
19+
Kubernetes.
20+
21+
This comes at a time where there is a proliferation of "AI Gateways" being used
22+
for AI Inference, and a strong need for focus and collaboration to ensure
23+
standards around this space so that Kubernetes users get the features they need
24+
in a consistent way on the platform.
25+
26+
### In Scope
27+
28+
Overall guidance for the WG is to control scope as much as is feasible. The WG
29+
should avoid AI-specific functionality where it can: instead favoring the
30+
addition of provisions that help with AI use-cases, but are otherwise normal
31+
networking facilities. Under that guidance, the following is in-scope:
32+
33+
* Providing definitions for networking related AI terms in a Kubernetes
34+
context.
35+
36+
* Defining important AI networking use-cases for Kubernetes users.
37+
38+
* Determining which common features and capabilities in the "AI Gateway" space
39+
need to be covered by Kubernetes standards and APIs according to user and
40+
implementation needs.
41+
42+
* Creating proposals for "AI Gateway" features and capabilities to the
43+
appropriate sub-projects.
44+
45+
* Propose new sub-projects if existing sub-projects are not sufficient.
46+
47+
### Out of Scope
48+
49+
* Developing whole "AI Gateway" solutions. This group will focus on
50+
enabling existing and new solutions to be more easily deployed and managed on
51+
Kubernetes, not adding any new production solutions maintained thereafter by
52+
upstream Kubernetes.
53+
54+
* Any specific kind of hardware support is generally out of scope.
55+
56+
* This group will not cover the entire spectrum of networking for AI. For
57+
instance: RDMA networks are generally out of scope.
58+
59+
## Deliverables
60+
61+
* A compendium of AI related networking definitions (e.g. "AI Gateway") and a
62+
key use-cases for Kubernetes users.
63+
64+
* Provide a space for collaboration and experimentation to determine the most
65+
viable features and capabilities that Kubernetes should support. If there is
66+
strong consensus on any particular ideas, the WG will facilitate and
67+
coordinate the delivery of proposals in the appropriate areas.
68+
69+
## Stakeholders
70+
71+
* SIG Network
72+
73+
## Roles and Organization Management
74+
75+
This working group adheres to the Roles and Organization Management outlined in
76+
[wg-governance] and opts-in to updates and modifications to [wg-governance].
77+
78+
[wg-governance]:https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
79+
80+
## Exit Criteria
81+
82+
The WG is done when its deliverables are complete, according to the defined
83+
scope and a list of key use cases and features agreed upon by the group.
84+
85+
Ideally we want the lifecycle of the WG to go something like this:
86+
87+
1. Determine definitions and key use cases for Kubernetes users and
88+
implementations, and document those.
89+
2. Determine a list of key features that Kubernetes needs to best support the
90+
defined use cases.
91+
3. For each feature in that list, make proposals which support them to the
92+
appropriate sub-projects OR propose new sub-projects if deemed necessary.
93+
4. Once the feature list is complete, leave behind some guidance and best
94+
practices for future implementations and then exit.

0 commit comments

Comments
 (0)