Add WG AI Integration #8519

mrunalp · 2025-07-15T00:04:21Z

This PR is to follow up from https://docs.google.com/document/d/13OJvWKGKZL0V4nPpv9anitL5je92FCdQyXePcrY2N84/edit?tab=t.0 to get WG AI Integration started.

cc: @ardaguclu @rushmash91 @zvonkok
Thanks for volunteering as chairs for the group! We hope to work with the broad community that has expressed interest in this WG.

cc: @derekwaynecarr @dims @johnbelamaric

k8s-ci-robot · 2025-07-15T00:04:30Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mrunalp
Once this PR has been reviewed and has the lgtm label, please assign madhavjivrajani for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

mrunalp · 2025-07-15T00:07:39Z

cc: @jpbetz @deads2k (API Machinery) @deads2k @liggitt (Auth) @janetkuo (Apps) @danwinship (Network) @soltysh (CLI)

zvonkok · 2025-07-15T00:13:49Z

👍🏼

Anutrix · 2025-07-15T00:20:00Z

wg-ai-integration/charter.md

+
+* Identify appropriate auth(z) patterns for AI connector identities, its
+ closest caller, and Kubernetes RBAC.
+ closest caller, and Kubernetes RBAC.


Typo. Same as previous line.

Fixed, thanks!

Anutrix · 2025-07-15T00:22:21Z

wg-ai-integration/charter.md

+ 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 integration with existing SIGs).


Is the space at the start of these 4 lines intentional? The line before it doesn't have a space at the start.

Fixed, thanks!

zvonkok · 2025-07-15T00:22:22Z

sigs.yaml

+      email: [email protected]
+    - github: zvonkok
+      name: Zvonko Kaiser
+      company: Nvidia


Suggested change

company: Nvidia

company: NVIDIA

janetkuo · 2025-07-15T00:49:18Z

sigs.yaml

+  meetings:
+  - description: WG AI Integration Weekly Meeting
+    day: Wednesday
+    time: 9:30 Amazon


Suggested change

time: 9:30 Amazon

time: 9:30

Fixed, thanks!

Signed-off-by: Mrunal Patel <[email protected]>

k8s-ci-robot · 2025-07-15T04:23:52Z

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes org. You can then trigger verification by writing /verify-owners in a comment.

rushmash91
- User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

cblecker · 2025-07-16T14:39:33Z

/hold
for review

rr-paras-patel · 2025-07-17T18:36:30Z

Hi Team, I missed our last meeting. i am interested in contributing and maintaining this area. can i get my self added as committee member here ?
I am one of the active Maintainer of most popular k8s mcp server and running Platform Engineering team at Rakuten.

danwinship · 2025-07-17T19:20:08Z

wg-ai-integration/charter.md

+* SIG Apps
+* SIG Auth
+* SIG CLI
+* SIG Network


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 ?

One area where SIG Network could have input is for protocol (such as MCP) proxies or gateways.
I can add that to the list of areas to explore.

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

mrunalp · 2025-07-18T17:24:12Z

@rr-paras-patel Hi! You are very welcome to participate in the WG :) We do want to limit number of chairs to 3 for now. Note that one doesn't have to be a chair to participate. The intent for the WG is to be wide open to the community. The chairs are responsible for organizing the WG.

aojea · 2025-07-18T18:11:21Z

wg-ai-integration/charter.md

+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


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

with the Kubernetes project (existing SIGs, new SIG, or totally external

* Recommend an appropriate go forward governance model for AI Integrations

with the Kubernetes project or totally external

to Kubernetes.

it is implicit that it must be owned by a SIG if is within the kubernetes project

aojea · 2025-07-18T18:22:25Z

wg-ai-integration/charter.md

+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


similar comment to https://github.com/kubernetes/community/pull/8519/files#r2216631198

Suggested change

own governance model to provide proper stewardship within the project (new SIG or

* Recommend an appropriate go forward governance model for AI Integrations

with the Kubernetes project or totally external to Kubernetes.

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

aojea · 2025-07-18T18:34:31Z

wg-ai-integration/README.md

+## Organizers
+
+* Arda Guclu (**[@ardaguclu](https://github.com/ardaguclu)**), Red Hat
+* Arush Sharma (**[@rushmash91](https://github.com/rushmash91)**), Amazon


@rushmash91 can you work on getting your membership to be able to meet the requirements?

Please note that all working group organizers and holders of other leadership roles must be community members.

https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md

Sure! Working on it!

k8s-ci-robot requested review from ardaguclu and derekwaynecarr July 15, 2025 00:04

Anutrix reviewed Jul 15, 2025

View reviewed changes

zvonkok reviewed Jul 15, 2025

View reviewed changes

mrunalp force-pushed the wg_ai_integration branch 3 times, most recently from 36508bc to 4be737a Compare July 15, 2025 00:25

janetkuo reviewed Jul 15, 2025

View reviewed changes

kannon92 mentioned this pull request Jul 15, 2025

Introduce WG Checkpoint Restore #8508

Draft

Add WG AI Integration

9add742

Signed-off-by: Mrunal Patel <[email protected]>

mrunalp force-pushed the wg_ai_integration branch from 4be737a to 9add742 Compare July 15, 2025 04:23

enj added this to SIG Auth Jul 15, 2025

enj moved this to Needs Triage in SIG Auth Jul 15, 2025

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 16, 2025

danwinship reviewed Jul 17, 2025

View reviewed changes

aojea reviewed Jul 18, 2025

View reviewed changes

	own governance model to provide proper stewardship within the project (new SIG or
	* Recommend an appropriate go forward governance model for AI Integrations
	with the Kubernetes project or totally external to Kubernetes.

Add WG AI Integration #8519

Are you sure you want to change the base?

Add WG AI Integration #8519

Conversation

mrunalp commented Jul 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-ci-robot commented Jul 15, 2025

Uh oh!

mrunalp commented Jul 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zvonkok commented Jul 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

k8s-ci-robot commented Jul 15, 2025

Uh oh!

cblecker commented Jul 16, 2025

Uh oh!

rr-paras-patel commented Jul 17, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mrunalp commented Jul 18, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mrunalp commented Jul 15, 2025 •

edited

Loading

mrunalp commented Jul 15, 2025 •

edited

Loading