Skip to content

Commit 84d372b

Browse files
committed
add WG AI Gateway
Signed-off-by: Shane Utt <[email protected]>
1 parent b7c5e66 commit 84d372b

File tree

8 files changed

+197
-0
lines changed

8 files changed

+197
-0
lines changed

OWNERS_ALIASES

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,12 @@ aliases:
125125
- claudiubelu
126126
- marosset
127127
- zylxjtu
128+
wg-ai-gateway-leads:
129+
- keithmattix
130+
- kfswain
131+
- nirrozenbaum
132+
- shaneutt
133+
- xunzhuo
128134
wg-batch-leads:
129135
- kannon92
130136
- mwielgus

liaisons.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ members will assume one of the departing members groups.
5454
| [SIG Testing](sig-testing/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
5555
| [SIG UI](sig-ui/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
5656
| [SIG Windows](sig-windows/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
57+
| [WG AI Gateway](wg-ai-gateway/README.md) | Shane Utt (**[@shaneutt](https://github.com/shaneutt)**) |
5758
| [WG Batch](wg-batch/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
5859
| [WG Data Protection](wg-data-protection/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
5960
| [WG Device Management](wg-device-management/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |

sig-list.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
6161

6262
| Name | Label | Stakeholder SIGs |Organizers | Contact | Meetings |
6363
|------|-------|------------------|-----------|---------|----------|
64+
|[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>* [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]()|* 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>
6465
|[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>
6566
|[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>
6667
|[Device Management](wg-device-management/README.md)|[device-management](https://github.com/kubernetes/kubernetes/labels/wg%2Fdevice-management)|* Architecture<br>* Autoscaling<br>* Network<br>* Node<br>* Scheduling<br>|* [John Belamaric](https://github.com/johnbelamaric), Google<br>* [Kevin Klues](https://github.com/klueska), NVIDIA<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-device-management)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-device-management)|* Regular WG Meeting (Asia/Europe): [Wednesdays at 9:00 CET (Central European Time) (biweekly)](https://zoom.us/j/97238699195?pwd=cy9IMm1ZeERtRlJ3VS8yWUxHUWIrQT09)<br>* Regular WG Meeting (Europe/America): [Tuesdays at 8:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/97238699195?pwd=cy9IMm1ZeERtRlJ3VS8yWUxHUWIrQT09)<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: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3529,6 +3529,55 @@ sigs:
35293529
- https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-dev-tools/master/OWNERS
35303530
- https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/OWNERS
35313531
workinggroups:
3532+
- dir: wg-ai-gateway
3533+
name: AI Gateway
3534+
mission_statement: >
3535+
The AI Gateway Working Group focuses on the intersection of AI and networking,
3536+
particularly in the context of extending load-balancer, gateway and proxy technologies
3537+
to manage and route traffic for AI Inference.
3538+
3539+
charter_link: charter.md
3540+
stakeholder_sigs:
3541+
- Network
3542+
label: ai-gateway
3543+
leadership:
3544+
chairs:
3545+
- github: keithmattix
3546+
name: Keith Mattix
3547+
company: Microsoft
3548+
3549+
- github: kfswain
3550+
name: Kellen Swain
3551+
company: Google
3552+
3553+
- github: nirrozenbaum
3554+
name: Nir Rozenbaum
3555+
company: IBM
3556+
3557+
- github: shaneutt
3558+
name: Shane Utt
3559+
company: Red Hat
3560+
3561+
- github: xunzhuo
3562+
name: Xunzhuo
3563+
company: Tencent
3564+
3565+
meetings:
3566+
- description: WG AI Gateway Bi-Weekly Meeting (Earlier Option)
3567+
day: Monday
3568+
time: 12PM
3569+
tz: UTC
3570+
frequency: bi-weekly
3571+
- description: WG AI Gateway Bi-Weekly Meeting (Later Option)
3572+
day: Thursday
3573+
time: 6PM
3574+
tz: UTC
3575+
frequency: bi-weekly
3576+
contact:
3577+
slack: wg-ai-gateway
3578+
liaison:
3579+
github: shaneutt
3580+
name: Shane Utt
35323581
- dir: wg-batch
35333582
name: Batch
35343583
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: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
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+
* 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).
20+
* 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).
21+
22+
## Organizers
23+
24+
* Keith Mattix (**[@keithmattix](https://github.com/keithmattix)**), Microsoft
25+
* Kellen Swain (**[@kfswain](https://github.com/kfswain)**), Google
26+
* Nir Rozenbaum (**[@nirrozenbaum](https://github.com/nirrozenbaum)**), IBM
27+
* Shane Utt (**[@shaneutt](https://github.com/shaneutt)**), Red Hat
28+
* Xunzhuo (**[@xunzhuo](https://github.com/xunzhuo)**), Tencent
29+
30+
## Contact
31+
- Slack: [#wg-ai-gateway](https://kubernetes.slack.com/messages/wg-ai-gateway)
32+
- [Mailing list]()
33+
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fai-gateway)
34+
- Steering Committee Liaison: Shane Utt (**[@shaneutt](https://github.com/shaneutt)**)
35+
<!-- BEGIN CUSTOM CONTENT -->
36+
37+
<!-- 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 capabitilies 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)