Skip to content

Commit

Permalink
WG serving proposal
Browse files Browse the repository at this point in the history
  • Loading branch information
SergeyKanzhelev committed Apr 20, 2024
1 parent 70fd52b commit 49e6111
Show file tree
Hide file tree
Showing 14 changed files with 184 additions and 0 deletions.
3 changes: 3 additions & 0 deletions OWNERS_ALIASES
Expand Up @@ -141,6 +141,9 @@ aliases:
wg-policy-leads:
- JimBugwadia
- rficcaglia
wg-serving-leads:
- SergeyKanzhelev
- TBD
wg-structured-logging-leads:
- mengjiao-liu
- pohly
Expand Down
1 change: 1 addition & 0 deletions liaisons.md
Expand Up @@ -60,6 +60,7 @@ members will assume one of the departing members groups.
| [WG IoT Edge](wg-iot-edge/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
| [WG LTS](wg-lts/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
| [WG Policy](wg-policy/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
| [WG Serving](wg-serving/README.md) | TODO TODO (**[@TODO](https://github.com/TODO)**) |
| [WG Structured Logging](wg-structured-logging/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
| [Committee Code of Conduct](committee-code-of-conduct/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
| [Committee Security Response](committee-security-response/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
Expand Down
1 change: 1 addition & 0 deletions sig-apps/README.md
Expand Up @@ -59,6 +59,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
The following [working groups][working-group-definition] are sponsored by sig-apps:
* [WG Batch](/wg-batch)
* [WG Data Protection](/wg-data-protection)
* [WG Serving](/wg-serving)


## Subprojects
Expand Down
1 change: 1 addition & 0 deletions sig-architecture/README.md
Expand Up @@ -59,6 +59,7 @@ The following [working groups][working-group-definition] are sponsored by sig-ar
* [WG API Expression](/wg-api-expression)
* [WG LTS](/wg-lts)
* [WG Policy](/wg-policy)
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
1 change: 1 addition & 0 deletions sig-autoscaling/README.md
Expand Up @@ -43,6 +43,7 @@ The Chairs of the SIG run operations and processes governing the SIG.

The following [working groups][working-group-definition] are sponsored by sig-autoscaling:
* [WG Batch](/wg-batch)
* [WG Serving](/wg-serving)


## Subprojects
Expand Down
1 change: 1 addition & 0 deletions sig-instrumentation/README.md
Expand Up @@ -53,6 +53,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
## Working Groups

The following [working groups][working-group-definition] are sponsored by sig-instrumentation:
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
1 change: 1 addition & 0 deletions sig-list.md
Expand Up @@ -67,6 +67,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[IoT Edge](wg-iot-edge/README.md)|[iot-edge](https://github.com/kubernetes/kubernetes/labels/wg%2Fiot-edge)|* Multicluster<br>* Network<br>|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Cindy Xing](https://github.com/cindyxing), Microsoft<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* APAC WG Meeting: [Wednesdays at 5:00 UTC (every four weeks)](https://zoom.us/j/91251176046?pwd=cmdqclovM3R3eDB1VlpuL1ZGU1hnZz09)<br>* Regular WG Meeting (Pacific Time): [Wednesdays at 09:00 PT (every four weeks)](https://zoom.us/j/92778512626?pwd=MXhlemwvYnhkQmkxeXllQ0Z5VGs4Zz09)<br>
|[LTS](wg-lts/README.md)|[lts](https://github.com/kubernetes/kubernetes/labels/wg%2Flts)|* Architecture<br>* Cluster Lifecycle<br>* K8s Infra<br>* Release<br>* Security<br>* Testing<br>|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-lts)|* Regular WG Meeting: [Tuesdays at 07:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/92480197536?pwd=dmtSMGJRQmNYYTIyZkFlQ25JRngrdz09)<br>
|[Policy](wg-policy/README.md)|[policy](https://github.com/kubernetes/kubernetes/labels/wg%2Fpolicy)|* Architecture<br>* Auth<br>* Multicluster<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Jim Bugwadia](https://github.com/JimBugwadia), Kyverno/Nirmata<br>* [Robert Ficcaglia](https://github.com/rficcaglia), SunStone<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 8:00 PT (Pacific Time) (semimonthly)](https://zoom.us/j/7375677271)<br>
|[Serving](wg-serving/README.md)|[serving](https://github.com/kubernetes/kubernetes/labels/wg%2Fserving)|* Apps<br>* Architecture<br>* Autoscaling<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Sergey Kanzhelev](https://github.com/SergeyKanzhelev), Google<br>* [TBD](https://github.com/TBD), TBD<br>|* [Slack](https://kubernetes.slack.com/messages/wg-serving)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-serving)|* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=TODO)): [TODOs at TODO PT (Pacific Time) (monthly)](https://zoom.us/j/TODO)<br>
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Mengjiao Liu](https://github.com/mengjiao-liu), DaoCloud<br>* [Patrick Ohly](https://github.com/pohly), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|

### Committees
Expand Down
1 change: 1 addition & 0 deletions sig-network/README.md
Expand Up @@ -74,6 +74,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
The following [working groups][working-group-definition] are sponsored by sig-network:
* [WG IoT Edge](/wg-iot-edge)
* [WG Policy](/wg-policy)
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
1 change: 1 addition & 0 deletions sig-node/README.md
Expand Up @@ -54,6 +54,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
The following [working groups][working-group-definition] are sponsored by sig-node:
* [WG Batch](/wg-batch)
* [WG Policy](/wg-policy)
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
1 change: 1 addition & 0 deletions sig-scheduling/README.md
Expand Up @@ -64,6 +64,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
The following [working groups][working-group-definition] are sponsored by sig-scheduling:
* [WG Batch](/wg-batch)
* [WG Policy](/wg-policy)
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
1 change: 1 addition & 0 deletions sig-storage/README.md
Expand Up @@ -58,6 +58,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
The following [working groups][working-group-definition] are sponsored by sig-storage:
* [WG Data Protection](/wg-data-protection)
* [WG Policy](/wg-policy)
* [WG Serving](/wg-serving)
* [WG Structured Logging](/wg-structured-logging)


Expand Down
41 changes: 41 additions & 0 deletions sigs.yaml
Expand Up @@ -3467,6 +3467,47 @@ workinggroups:
liaison:
github: pohly
name: Patrick Ohly
- dir: wg-serving
name: Serving
mission_statement: >
Discuss and enhance the support of inference serving for accelerated workloads
in Kubernetes. Make Kubernetes the natural choice for hosting production inference
reliably, and improve all serving workloads along the way.
charter_link: charter.md
stakeholder_sigs:
- Apps
- Architecture
- Autoscaling
- Instrumentation
- Network
- Node
- Scheduling
- Storage
label: serving
leadership:
chairs:
- github: SergeyKanzhelev
name: Sergey Kanzhelev
company: Google
- github: TBD
name: TBD
company: TBD
meetings:
- description: Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=TODO))
day: TODO
time: TODO
tz: PT (Pacific Time)
frequency: monthly
url: https://zoom.us/j/TODO
archive_url: https://docs.google.com/document/d/1aExJFtaLnO-TM6_2uILgI8NI0IjOm7FcwLABBKEMEo0/edit
recordings_url: https://www.youtube.com/playlist?list=TODO
contact:
slack: wg-serving
mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-serving
liaison:
github: TODO
name: TODO TODO
- dir: wg-structured-logging
name: Structured Logging
mission_statement: >
Expand Down
43 changes: 43 additions & 0 deletions wg-serving/README.md
@@ -0,0 +1,43 @@
<!---
This is an autogenerated file!
Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
--->
# Serving Working Group

Discuss and enhance the support of inference serving for accelerated workloads in Kubernetes. Make Kubernetes the natural choice for hosting production inference reliably, and improve all serving workloads along the way.

The [charter](charter.md) defines the scope and governance of the Serving Working Group.

## Stakeholder SIGs
* [SIG Apps](/sig-apps)
* [SIG Architecture](/sig-architecture)
* [SIG Autoscaling](/sig-autoscaling)
* [SIG Instrumentation](/sig-instrumentation)
* [SIG Network](/sig-network)
* [SIG Node](/sig-node)
* [SIG Scheduling](/sig-scheduling)
* [SIG Storage](/sig-storage)

## Meetings
*Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-serving) for the group will typically add invites for the following meetings to your calendar.*
* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=TODO)): [TODOs at TODO PT (Pacific Time)](https://zoom.us/j/TODO) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=TODO&tz=PT%20%28Pacific%20Time%29).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1aExJFtaLnO-TM6_2uILgI8NI0IjOm7FcwLABBKEMEo0/edit).
* [Meeting recordings](https://www.youtube.com/playlist?list=TODO).

## Organizers

* Sergey Kanzhelev (**[@SergeyKanzhelev](https://github.com/SergeyKanzhelev)**), Google
* TBD (**[@TBD](https://github.com/TBD)**), TBD

## Contact
- Slack: [#wg-serving](https://kubernetes.slack.com/messages/wg-serving)
- [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-serving)
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fserving)
- Steering Committee Liaison: TODO TODO (**[@TODO](https://github.com/TODO)**)
<!-- BEGIN CUSTOM CONTENT -->

<!-- END CUSTOM CONTENT -->
87 changes: 87 additions & 0 deletions wg-serving/charter.md
@@ -0,0 +1,87 @@
# WG Serving Charter

This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [wg-governance].

[Kubernetes Charter README]: /committee-steering/governance/README.md

## Scope

Discuss and enhance the support for AI/ML inference workloads in Kubernetes.


### In scope

- Gather requirements for serving workloads (inference primarily, but benefiting
other non-batch use cases where possible) that have broad community alignment
from practitioners, distros, and vendors. Provide concrete input to other SIGs
and WGs around needs for identified requirements. Do it in partnership
with existing ecosystem projects like kServe, Seldon, Kaito, and
others to identify, extract, or implement common shared problems (like Kueue
abstracted deferred scheduling for multiple batch frameworks).
- Specific areas of improvement include:
- Directly improve key kubernetes workload controllers when used with
accelerators and the most common inference serving frameworks and model
servers.
- Explore new projects that improve orchestration, scaling, and load balancing
of inference workloads and compose well with other workloads on Kubernetes
- Being able to run serving workloads safely while giving up
available slack capacity to batch frameworks

### Out of scope

- Training and batch inference, which are covered by WG Batch.
- Addition of new API kinds that serve a specific models. The focus should be on
general APIs that frameworks can build on top of.
- Ability to describe the workflows for serving workloads is out of scope,
Kubernetes will offer building blocks to MLOps platforms to build those.

## Stakeholders

Stakeholders in this working group span multiple SIGs that own parts of the
code in core kubernetes components and addons.

- SIG Apps as an primary SIG
- SIG Architecture
- SIG Node
- SIG Scheduling
- SIG Autoscaling
- SIG Network
- SIG Instrumentation
- SIG Storage

## Deliverables

The list of deliverables include the following high level features:

- To SIG Apps:
- Ability to express the model serving workloads with easy to understand logical
objects with the ability to scale to multi-host
- To SIG Scheduling and Autoscaling
- Faster scaling up and down
- Ability to preempt workloads
- To SIG Node:
- Runtime support for Pods preemption
- Runtime support for devices partitioning

## Roles and Organization Management

This wg adheres to the Roles and Organization Management outlined in [wg-governance]
and opts-in to updates and modifications to [wg-governance].

[wg-governance]: /committee-steering/governance/wg-governance.md

Additionally, the wg commits to:

- maintain a solid communication line between the Kubernetes groups and the wider CNCF community;
- submit a proposal to the KubeCon/CloudNativeCon maintainers track;

## Timelines and Disbanding

As a first mandate, the wg will define a roadmap in the first quarter of operation.
We believe there will be a set of features the Working Group can identify and deliver
that will enable the majority of frameworks operate natively on Kubernetes.

There is no expectations that the Working Group will be converted into SIG long term,
however, there is a chance that a separate project or a sizeable sub-component of SIG Apps can be
created as a result of a Working Group.

0 comments on commit 49e6111

Please sign in to comment.