Skip to content

add Kubernetes AI Conformance working group #8515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions OWNERS_ALIASES
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,11 @@ aliases:
- claudiubelu
- marosset
- zylxjtu
wg-ai-conformance-leads:
- janetkuo
- mfahlandt
- ritazh
- terrytangyuan
wg-batch-leads:
- kannon92
- mwielgus
Expand Down
1 change: 1 addition & 0 deletions sig-architecture/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
## Working Groups

The following [working groups][working-group-definition] are sponsored by sig-architecture:
* [WG AI Conformance](/wg-ai-conformance)
* [WG Device Management](/wg-device-management)
* [WG LTS](/wg-lts)
* [WG Serving](/wg-serving)
Expand Down
1 change: 1 addition & 0 deletions sig-list.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)

| Name | Label | Stakeholder SIGs |Organizers | Contact | Meetings |
|------|-------|------------------|-----------|---------|----------|
|[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: [Wednesdays at 09:00 PT (Pacific Time) (weekly)]()<br>
|[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>
|[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>
|[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>
Expand Down
1 change: 1 addition & 0 deletions sig-testing/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
## Working Groups

The following [working groups][working-group-definition] are sponsored by sig-testing:
* [WG AI Conformance](/wg-ai-conformance)
* [WG LTS](/wg-lts)


Expand Down
39 changes: 39 additions & 0 deletions sigs.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3526,6 +3526,45 @@ sigs:
- https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-dev-tools/master/OWNERS
- https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/OWNERS
workinggroups:
- dir: wg-ai-conformance
name: AI Conformance
mission_statement: >
The goal of this group is to define a standardized set of capabilities, APIs,
and configurations that a Kubernetes cluster must offer to reliably and efficiently
run AI/ML workloads.

charter_link: charter.md
stakeholder_sigs:
- Architecture
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this should list the same SIGs that are listed as stakeholders in your charter.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Member

@BenTheElder BenTheElder Jul 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO this should also have SIG testing given that a suite of tests is in scope.

cc @aojea @pohly

As a TL I am +1 to sponsor the WG.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, so does everybody agree to list only: SIG Architecture and SIG Testing for now? Please let me know so I can make the change and get this merged asap to start meeting

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 as SIG Testing TL.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 as SIG Arch Chair

- Testing
label: ai-conformance
leadership:
chairs:
- github: janetkuo
name: Janet Kuo
company: Google
email: [email protected]
- github: mfahlandt
name: Mario Fahlandt
company: Kubermatic GmbH
email: [email protected]
- github: ritazh
name: Rita Zhang
company: Microsoft
email: [email protected]
- github: terrytangyuan
name: Yuan Tang
company: Red Hat
email: [email protected]
meetings:
- description: Regular WG Meeting
day: Wednesday
time: "09:00"
tz: PT (Pacific Time)
frequency: weekly
contact:
slack: wg-ai-conformance
mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-ai-conformance
- dir: wg-batch
name: Batch
mission_statement: >
Expand Down
36 changes: 36 additions & 0 deletions wg-ai-conformance/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
<!---
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
--->
# AI Conformance Working Group

The goal of this group is to define a standardized set of capabilities, APIs, and configurations that a Kubernetes cluster must offer to reliably and efficiently run AI/ML workloads.

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

## Stakeholder SIGs
* [SIG Architecture](/sig-architecture)
* [SIG Testing](/sig-testing)

## Meetings
*Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-conformance) for the group will typically add invites for the following meetings to your calendar.*
* Regular WG Meeting: [Wednesdays at 09:00 PT (Pacific Time)]() (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09%3A00&tz=PT%20%28Pacific%20Time%29).

## Organizers

* Janet Kuo (**[@janetkuo](https://github.com/janetkuo)**), Google
* Mario Fahlandt (**[@mfahlandt](https://github.com/mfahlandt)**), Kubermatic GmbH
* Rita Zhang (**[@ritazh](https://github.com/ritazh)**), Microsoft
* Yuan Tang (**[@terrytangyuan](https://github.com/terrytangyuan)**), Red Hat

## Contact
- Slack: [#wg-ai-conformance](https://kubernetes.slack.com/messages/wg-ai-conformance)
- [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-conformance)
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fai-conformance)
<!-- BEGIN CUSTOM CONTENT -->

<!-- END CUSTOM CONTENT -->
43 changes: 43 additions & 0 deletions wg-ai-conformance/charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# WG Kubernetes AI Conformance Charter

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

## Scope

The goal of this group is to define a standardized set of capabilities, APIs, and configurations that a Kubernetes cluster must offer to reliably and efficiently run AI/ML workloads. This initiative aims to simplify AI/ML operations on Kubernetes, accelerate adoption, guarantee interoperability and portability for AI workloads, and enable ecosystem growth on an industry-standard foundation.

### In scope

#### Code, Binaries and Services

- The primary artifact will be the (working title for now) "CNCF Kubernetes AI Conformance" specification and a suite of tests to demonstrate conformance.

#### Cross-cutting and Externally Facing Processes

- The Working Group will consider its primary problem-solving objective complete upon the successful definition and initial adoption of a stable (working title for now) "CNCF Kubernetes AI Conformance" specification.
- Once the foundational conformance is established and widely recognized, the ongoing maintenance and evolution of the conformance would be evaluated, and could ideally transition to an existing or newly formed Special Interest Group (SIG) with a long-term charter, at which point the Working Group would dissolve.
Comment on lines +14 to +19
Copy link
Member

@aojea aojea Jul 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have certain doubts with this paragraph

The WG definition in https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md#is-it-a-working-group-yes-if
indicates clearly that a WG

It does not own any code

A suite of tests is code, and there is also references to

and could ideally transition to an existing or newly formed Special Interest Group (SIG) with a long-term charter

So, if this code is in kubernetes it has to be owned by a SIG before, as "transition" implies it was owned by someone before, and a WG can not be the owner as indicated before, we need to clarify this.

The reference to "newly formed Special Interest Group (SIG)" is tendentious and irrelevant to the work and scope of this WG, I do not think it should be here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Once the foundational conformance is established and widely recognized, the ongoing maintenance and evolution of the conformance would be evaluated, and could ideally transition to an existing or newly formed Special Interest Group (SIG) with a long-term charter, at which point the Working Group would dissolve.
- Once the foundational conformance is established and widely recognized, the ongoing maintenance and evolution of the conformance would be evaluated, and could ideally transition to a Special Interest Group (SIG) with a long-term charter, at which point the Working Group would dissolve.


### Out of scope

This WG is not responsible for maintenance and evolution of the conformance program, which will be run by the CNCF. Some aspects may be owned by existing SIGs (Architecture, Testing) alongside the CNCF, such as Kubernetes specific testing and tooling, and the pre-existing Kubernetes conformance definition and tests.

## Roles and Organization Management

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

### Additional responsibilities of Chairs

- The Working Group will have designated Chair(s) responsible for guiding discussions and ensuring progress.
- A note-taker will be assigned for each meeting, and active participation from all contributors will be encouraged.
- Agendas and meeting notes will be publicly accessible.

### Stakeholder SIGs

- SIG Architecture (Sponsoring SIG)
- SIG Testing


[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md