Add WG AI Integration #8519
+207
−0
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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-integration | ||
| name: AI Integration | ||
| mission_statement: > | ||
| The AI Integration Working Group focuses on enabling seamless integration of AI/ML | ||
| control planes with Kubernetes, as well as providing standardized patterns for | ||
| deploying, managing, and operating AI applications at scale on Kubernetes. | ||
|
|
||
| charter_link: charter.md | ||
| stakeholder_sigs: | ||
| - API Machinery | ||
| - Apps | ||
| - Architecture | ||
| - Auth | ||
| - CLI | ||
| - Network | ||
| label: ai-integration | ||
| leadership: | ||
| chairs: | ||
| - github: ardaguclu | ||
| name: Arda Guclu | ||
| company: Red Hat | ||
| email: [email protected] | ||
| - github: rushmash91 | ||
| name: Arush Sharma | ||
| company: Amazon | ||
| email: [email protected] | ||
| - github: zvonkok | ||
| name: Zvonko Kaiser | ||
| company: NVIDIA | ||
| email: [email protected] | ||
| meetings: | ||
| - description: WG AI Integration Weekly Meeting | ||
| day: Wednesday | ||
| time: "9:30" | ||
| tz: PT (Pacific Time) | ||
| frequency: weekly | ||
| contact: | ||
| slack: wg-ai-integration | ||
| mailing_list: https://groups.google.com/a/kubernetes.io/g/wg-ai-integration | ||
| - dir: wg-batch | ||
| name: Batch | ||
| mission_statement: > | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| # See the OWNERS docs at https://go.k8s.io/owners | ||
|
|
||
| reviewers: | ||
| - wg-ai-integration-leads | ||
| approvers: | ||
| - wg-ai-integration-leads | ||
| labels: | ||
| - wg/ai-integration |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| <!--- | ||
| 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 Integration Working Group | ||
|
|
||
| The AI Integration Working Group focuses on enabling seamless integration of AI/ML control planes with Kubernetes, as well as providing standardized patterns for deploying, managing, and operating AI applications at scale on Kubernetes. | ||
|
|
||
| The [charter](charter.md) defines the scope and governance of the AI Integration Working Group. | ||
|
|
||
| ## Stakeholder SIGs | ||
| * [SIG API Machinery](/sig-api-machinery) | ||
| * [SIG Apps](/sig-apps) | ||
| * [SIG Architecture](/sig-architecture) | ||
| * [SIG Auth](/sig-auth) | ||
| * [SIG CLI](/sig-cli) | ||
| * [SIG Network](/sig-network) | ||
|
|
||
| ## Meetings | ||
| *Joining the [mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-integration) for the group will typically add invites for the following meetings to your calendar.* | ||
| * WG AI Integration Weekly Meeting: [Wednesdays at 9:30 PT (Pacific Time)]() (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9%3A30&tz=PT%20%28Pacific%20Time%29). | ||
|
|
||
| ## Organizers | ||
|
|
||
| * Arda Guclu (**[@ardaguclu](https://github.com/ardaguclu)**), Red Hat | ||
| * Arush Sharma (**[@rushmash91](https://github.com/rushmash91)**), Amazon | ||
| * Zvonko Kaiser (**[@zvonkok](https://github.com/zvonkok)**), NVIDIA | ||
|
|
||
| ## Contact | ||
| - Slack: [#wg-ai-integration](https://kubernetes.slack.com/messages/wg-ai-integration) | ||
| - [Mailing list](https://groups.google.com/a/kubernetes.io/g/wg-ai-integration) | ||
| - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fai-integration) | ||
| <!-- BEGIN CUSTOM CONTENT --> | ||
|
|
||
| <!-- END CUSTOM CONTENT --> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,105 @@ | ||||||||||
| # WG AI Integration Charter | ||||||||||
|
|
||||||||||
| This charter adheres to the conventions described in the [Kubernetes Charter | ||||||||||
| README] and uses the Roles and Organization Management outlined in | ||||||||||
| [wg-governance]. | ||||||||||
|
|
||||||||||
| ## Scope | ||||||||||
|
|
||||||||||
| The AI Integration Working Group focuses on enabling seamless integration of | ||||||||||
| AI/ML control planes with Kubernetes, as well as providing standardized | ||||||||||
| patterns for deploying, managing, and operating AI applications at scale | ||||||||||
| on Kubernetes. | ||||||||||
|
|
||||||||||
| The Working Group will provide a forum for a broad engineering community to | ||||||||||
| give feedback to the project on challenges encountered when integrating with | ||||||||||
| Kubernetes. | ||||||||||
|
|
||||||||||
| This addresses a broad need with many end-users deploying complex AI systems, | ||||||||||
| AI/ML platform providers, Kubernetes distributions, and developers of | ||||||||||
| distributed AI applications facing these integration challenges. Standardizing | ||||||||||
| solutions in this space benefits the entire Kubernetes ecosystem. Adjacent | ||||||||||
| ecosystems could link to the outputs of this WG as a trusted vehicle for | ||||||||||
| supporting AI integrations with Kubernetes. | ||||||||||
|
|
||||||||||
| ### In scope | ||||||||||
|
|
||||||||||
| * Develop a shared community point of view and associated best practices | ||||||||||
| enabling AI agent (or multi-agent) systems to integrate with Kubernetes. | ||||||||||
|
|
||||||||||
| * Provide a forum for intersecting code experimentation in AI integration | ||||||||||
| space (to be provided externally of Kubernetes via LF/CNCF) and discussion | ||||||||||
| with the existing Kubernetes community. | ||||||||||
|
|
||||||||||
| * Recommend an appropriate go forward governance model for AI Integrations | ||||||||||
| with the Kubernetes project (existing SIGs, new SIG, or totally external | ||||||||||
|
There was a problem hiding this comment. Similar comment to the one I did in https://github.com/kubernetes/community/pull/8515/files#r2216446151 I don't think the references to existing SIGs or new SIGs are related to the proposal and are tendentious and irrelevant , we should rephrase this as
Suggested change
it is implicit that it must be owned by a SIG if is within the kubernetes project |
||||||||||
| to Kubernetes). | ||||||||||
|
|
||||||||||
| * Identify appropriate auth(z) patterns for AI connector identities, its | ||||||||||
| closest caller, and Kubernetes RBAC. | ||||||||||
|
|
||||||||||
| * Defining benchmarks on pros/cons of design approaches to meet user outcomes. | ||||||||||
|
|
||||||||||
| * Ensure security, observability, and policy enforcement can be consistently | ||||||||||
| applied across integrated systems (K8s and external Control Planes such as | ||||||||||
| LLMs) and AI integration applications. | ||||||||||
|
|
||||||||||
| * Define potential enhancements to API conventions to scale AI integration | ||||||||||
| patterns that respect data privacy and safety concerns during our design | ||||||||||
| process. | ||||||||||
|
|
||||||||||
| * Reduce the complexity and custom development required for deploying, | ||||||||||
| building and managing connectors of kubernetes API with AI agent ecosystems. | ||||||||||
|
|
||||||||||
| ### Out of Scope | ||||||||||
|
|
||||||||||
| * Development of AI/ML frameworks or applications | ||||||||||
| * General-purpose workload management not specific to AI/ML | ||||||||||
| * Deploying inference workloads on Kubernetes (which is covered by WG Serving) | ||||||||||
| * Manage accelerator devices (which is covered by WG Device Management) | ||||||||||
|
|
||||||||||
| ## Deliverables | ||||||||||
|
|
||||||||||
| * The WG will provide space for collaboration and experimentation. If/when any | ||||||||||
| solid ideas emerge that require changes to Kubernetes (for example, updates | ||||||||||
| to kubectl for AI consumption), the WG will facilitate and coordinate the delivery | ||||||||||
| of KEPs and their implementations by the participating SIGs. | ||||||||||
| * Interim artifacts will include documents capturing use cases, requirements, | ||||||||||
| integration architecture designs, and AI application communication patterns. | ||||||||||
| * Establish best practices document for AI tool integration with Kubernetes and | ||||||||||
| a clear recommendation if/what set of reference tools may best fit in | ||||||||||
| Kubernetes project itself informed from data driven experimentation with | ||||||||||
| appropriate governance model. | ||||||||||
|
|
||||||||||
| ## Stakeholders | ||||||||||
|
|
||||||||||
| * SIG Architecture | ||||||||||
| * SIG API Machinery | ||||||||||
| * SIG Apps | ||||||||||
| * SIG Auth | ||||||||||
| * SIG CLI | ||||||||||
| * SIG Network | ||||||||||
|
There was a problem hiding this comment. The big areas where SIG Network has been hearing about / dealing with AI are DRA (aka "Manage accelerator devices", which is marked out-of-scope) and inference-related Gateway features (which would seem to fall under "Deploying inference workloads", which is also marked out-of-scope, and which is the subject of a different AI WG proposal anyway). None of the things you list as "In scope" above seem like they need input from SIG Network. @kubernetes/sig-network-leads ? There was a problem hiding this comment. One area where SIG Network could have input is for protocol (such as MCP) proxies or gateways. There was a problem hiding this comment. I defer to Dan, I really not very familiar with these protocols you mention but it seems to me both WG-Serving and the AI-GW proposal Dan is indicating will overlap on that area |
||||||||||
|
|
||||||||||
| ## Roles and Organization Management | ||||||||||
|
|
||||||||||
| This working group adheres to the Roles and Organization Management outlined in | ||||||||||
| [wg-governance] and opts-in to updates and modifications to [wg-governance]. | ||||||||||
|
|
||||||||||
| ## Exit Criteria | ||||||||||
|
|
||||||||||
| The WG is done if/when a shared recommendation is in place for how the Kubernetes | ||||||||||
| project should or should not integrate with these emergent systems. This could | ||||||||||
| include a recommendation for Kubernetes to adopt and/or evolve tools (e.g. MCP | ||||||||||
| connectors, benchmark or environment validation tooling, etc.) and evolve its | ||||||||||
| own governance model to provide proper stewardship within the project (new SIG or | ||||||||||
|
There was a problem hiding this comment. similar comment to https://github.com/kubernetes/community/pull/8519/files#r2216631198
Suggested change
I know the idea of a new SIG for AI is floating around, but I do think is better and healthier if this is discussed widely and independently with more realistic dapatpoints and clearly defining the bounderies with existing SIGs that instead of start leaking into the WG proposals |
||||||||||
| integration with existing SIGs). | ||||||||||
|
|
||||||||||
| The working group will disband when the KEPs resulting from these discussions | ||||||||||
| have reached a terminal state. When the core functionality for AI workload | ||||||||||
| management reaches GA, we will evaluate whether the working group should | ||||||||||
| be disbanded and any remaining KEPs be left to the management of their owning | ||||||||||
| SIGs. | ||||||||||
|
|
||||||||||
| [wg-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md | ||||||||||
| [Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md | ||||||||||
|
|
||||||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rushmash91 can you work on getting your membership to be able to meet the requirements?
https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! Working on it!