-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
base: master
Are you sure you want to change the base?
Changes from all commits
3ed496b
e35c899
00be35b
5c82784
65f7742
e051457
de92136
c509fa4
485c874
dc732ff
de0879b
bd87281
1337cdf
68cf397
f9bd39f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 as SIG Testing TL. There was a problem hiding this comment. Choose a reason for hiding this commentThe 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: > | ||
|
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). | ||
fedebongio marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## 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 --> |
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
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
A suite of tests is code, and there is also references to
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. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
### 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) | ||||||
fedebongio marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
- 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 |
Uh oh!
There was an error while loading. Please reload this page.