Add WG AI Integration

mrunalp · mrunalp · commit 637a95049bd5 · 2025-08-01T11:42:36.000-07:00
Signed-off-by: Mrunal Patel &lt;mrunalp@gmail.com&gt;
diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES
@@ -130,6 +130,10 @@ aliases:
     - mfahlandt
     - ritazh
     - terrytangyuan
+  wg-ai-integration-leads:
+    - ardaguclu
+    - rushmash91
+    - zvonkok
   wg-batch-leads:
     - kannon92
     - mwielgus
diff --git a/liaisons.md b/liaisons.md
@@ -55,6 +55,7 @@ members will assume one of the departing members groups.
 | [SIG UI](sig-ui/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
 | [SIG Windows](sig-windows/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
 | [WG AI Conformance](wg-ai-conformance/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
+| [WG AI Integration](wg-ai-integration/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
 | [WG Batch](wg-batch/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
 | [WG Data Protection](wg-data-protection/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
 | [WG Device Management](wg-device-management/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
diff --git a/sig-api-machinery/README.md b/sig-api-machinery/README.md
@@ -54,6 +54,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
 ## Working Groups
 
 The following [working groups][working-group-definition] are sponsored by sig-api-machinery:
+* [WG AI Integration](/wg-ai-integration)
 * [WG Structured Logging](/wg-structured-logging)
 
 
diff --git a/sig-apps/README.md b/sig-apps/README.md
@@ -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-apps:
+* [WG AI Integration](/wg-ai-integration)
 * [WG Batch](/wg-batch)
 * [WG Data Protection](/wg-data-protection)
 * [WG Node Lifecycle](/wg-node-lifecycle)
diff --git a/sig-architecture/README.md b/sig-architecture/README.md
@@ -57,6 +57,7 @@ The Chairs of the SIG run operations and processes governing the SIG.
 
 The following [working groups][working-group-definition] are sponsored by sig-architecture:
 * [WG AI Conformance](/wg-ai-conformance)
+* [WG AI Integration](/wg-ai-integration)
 * [WG Device Management](/wg-device-management)
 * [WG LTS](/wg-lts)
 * [WG Serving](/wg-serving)
diff --git a/sig-auth/README.md b/sig-auth/README.md
@@ -62,6 +62,12 @@ subprojects, and resolve cross-subproject technical issues and decisions.
     - [@kubernetes/sig-auth-test-failures](https://github.com/orgs/kubernetes/teams/sig-auth-test-failures) - Test Failures and Triage
 - Steering Committee Liaison: Patrick Ohly (**[@pohly](https://github.com/pohly)**)
 
+## Working Groups
+
+The following [working groups][working-group-definition] are sponsored by sig-auth:
+* [WG AI Integration](/wg-ai-integration)
+
+
 ## Subprojects
 
 The following [subprojects][subproject-definition] are owned by sig-auth:
diff --git a/sig-cli/README.md b/sig-cli/README.md
@@ -63,6 +63,7 @@ subprojects, and resolve cross-subproject technical issues and decisions.
 ## Working Groups
 
 The following [working groups][working-group-definition] are sponsored by sig-cli:
+* [WG AI Integration](/wg-ai-integration)
 * [WG Node Lifecycle](/wg-node-lifecycle)
 
 
diff --git a/sig-list.md b/sig-list.md
@@ -62,6 +62,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: [Thursdays at 10:00 PT (Pacific Time) (weekly)]()<br>
+|[AI Integration](wg-ai-integration/README.md)|[ai-integration](https://github.com/kubernetes/kubernetes/labels/wg%2Fai-integration)|* API Machinery<br>* Apps<br>* Architecture<br>* Auth<br>* CLI<br>|* [Arda Guclu](https://github.com/ardaguclu), Red Hat<br>* [Arush Sharma](https://github.com/rushmash91), Amazon<br>* [Zvonko Kaiser](https://github.com/zvonkok), NVIDIA<br>|* [Slack](https://kubernetes.slack.com/messages/wg-ai-integration)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-ai-integration)|* WG AI Integration Weekly Meeting: [Wednesdays at 9:30 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>
diff --git a/sigs.yaml b/sigs.yaml
@@ -3567,6 +3567,47 @@ workinggroups:
     liaison:
       github: pohly
       name: Patrick Ohly
+- 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
+  label: ai-integration
+  leadership:
+    chairs:
+    - github: ardaguclu
+      name: Arda Guclu
+      company: Red Hat
+      email: ardaguclu@gmail.com
+    - github: rushmash91
+      name: Arush Sharma
+      company: Amazon
+      email: arushsharma91@gmail.com
+    - github: zvonkok
+      name: Zvonko Kaiser
+      company: NVIDIA
+      email: zkaiser@nvidia.com
+  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
+    liaison:
+      github: pacoxu
+      name: Paco Xu 徐俊杰
 - dir: wg-batch
   name: Batch
   mission_statement: >
diff --git a/wg-ai-integration/OWNERS b/wg-ai-integration/OWNERS
@@ -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
diff --git a/wg-ai-integration/README.md b/wg-ai-integration/README.md
@@ -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)
+
+## 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)
+- Steering Committee Liaison: Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**)
+<!-- BEGIN CUSTOM CONTENT -->
+
+<!-- END CUSTOM CONTENT -->
diff --git a/wg-ai-integration/charter.md b/wg-ai-integration/charter.md
@@ -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 and discussion with the existing Kubernetes community.
+
+* Recommend an appropriate go forward governance model for AI Integrations
+with the Kubernetes project.
+
+* 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. Consider alternative API patterns that could be a better fit for
+AI enablement.
+
+* Explore patterns for efficient network access to emergent protocols such
+as MCP/A2A via proxies or gateways.
+
+* 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
+
+## 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 or outside.
+
+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
