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

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!

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

Thanks for the review. I added an item for this in the charter.

So do we still need sig-network here or not? And where is the updated point, I can't find it 😅

@aojea what are your specific concerns here?

What are we currently doing with these WG

WG Device Management

WG Node Lifecycle

WG Serving

WG Structured Logging

Are we actively involved? Should we reduce this list? I know dev-mgmt, however are we as sig-net still playing a daily role in this?

Let me try to answer, those WG touch areas from the SIG Network charter, node lifecycle with endpoints, device management with network endpoints, serving as inference ... we asked a fair question on what is the overlap with SIG network charter and the answer is A2A and MCP protocols that are the same as websocket, is not in SIG network charter... I dont have more interest than resolving a conversation, and I talked with mrunal in private to clarify... If any SIG network lead had approved without an unresolved conversation I would not have any objections, I trust other to make the call they think is good for the SIG ... But I found surprising to approve when the conversation was open and waiting for an answer

I believe @shaneutt had a distinction between the current AI related working groups and the proposed. The question is fair, I am not contesting that, more asking for information on how to appropriately prioritize. We should have clear defined boundaries, however slight overlap isn't a bad thing at all. Shane is currently OOF, we should give him the benefit of the doubt this comment was missed? @shaneutt if you could address the concern from @danwinship? In the interest of transparency lets keep all conversations related to this PR here.

Let me explain myself better, I'm totally in favor of this WG and I was on my way to +1 from my steering hat thinking this conversation was solved. This WG is going to be created with or without SIG Network, there are already 5 SIGs sponsoring it so let's not make a big drama of this

SIG API Machinery

SIG Apps

SIG Architecture

SIG Auth

SIG CLI

Now, from the SIG Network hat, what is the role of SIG Network here? and as Dan correctly pointed out, we already have another WG on this area and a proposal for a new WG #8519 (comment)

So, if you say SIG Network has a role here because of foo and does not intersect with any of the other WG then it is ok .... BUT at one point WGs want their things to get done and then go to the SIGs ... and I really want to avoid that in SIG Network we need to deal with conflicts of interest between WGs, because that burns people and breaks communities, people that get frustrated because they were working on the WG with one goal and people that has to say no or has to choose between competing implementation ... this mean that we didn't do our work as leads on reviewing the WG proposal, that is what we should do here, be objective and talk and discuss and agree and review thoroughly for the best of the project ...

I just dropped SIG Network from the list. I would leave it up to sig-network leads if/how they engage with the WG. Thanks!

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.

mrunalp · 2025-07-30T18:51:14Z

wg-ai-integration/charter.md

+process. Consider alternative API patterns that could be a better fit for
+AI enablement.
+
+* Explore patterns for efficient network access to emergent protocols such


@soltysh Here is the point related to networking :)

Thank you, I've seen that, but still missed it 😅

soltysh · 2025-07-31T10:55:27Z

@mrunalp get the acks from sponsoring sigs, and update liaison with Paco's name, then ping steering again for a re-review :)

dims · 2025-07-31T15:46:48Z

+1 from me with SIG-Arch hat on.

ardaguclu · 2025-07-31T16:11:45Z

+1 from me for SIG-CLI

johnbelamaric · 2025-07-31T16:20:47Z

+1 from me for SIG Arch

jpbetz · 2025-07-31T21:00:40Z

+1 for SIG API Machinery

janetkuo

+1 from SIG Apps!

shaneutt · 2025-07-31T21:25:20Z

+1 from SIG Network

mrunalp · 2025-07-31T21:30:54Z

@soltysh I believe we have the ACKs from the sigs (Thanks folks :) ) so we should be ready for re-review :) @liggitt had previously acked in https://docs.google.com/document/d/13OJvWKGKZL0V4nPpv9anitL5je92FCdQyXePcrY2N84/edit?tab=t.0 for SIG-Auth and @deads2k (API/Auth) has also supported in this PR. Thanks!

soltysh

/lgtm
/approve
from steering

/hold
for other steering members to 👍 before merging this

@mrunalp one tiny nit, I don't see explicit sig-auth ack, unless we're counting @deads2k as both sig-apimachinery and sig-auth, and it sayd it's waiting triage from sig-auth.

aojea · 2025-08-01T14:37:35Z

+1 from SIG Network

~~Sig Network still has to be discussed #8519 (comment)~~

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

k8s-ci-robot · 2025-08-01T18:43:04Z

New changes are detected. LGTM label has been removed.

aojea · 2025-08-01T18:45:24Z

+1 (steering)

saschagrunert

+1 (steering)

I’m happy to move forward with this proposal. 👍

k8s-ci-robot · 2025-08-01T21:47:14Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, janetkuo, mrunalp, saschagrunert, soltysh

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

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [saschagrunert,soltysh]

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

liggitt · 2025-08-02T15:13:51Z

I don't see explicit sig-auth ack, unless we're counting @deads2k as both sig-apimachinery and sig-auth, and it sayd it's waiting triage from sig-auth

+1 for sig-auth

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

Open

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

mrunalp force-pushed the wg_ai_integration branch from 0fa40ba to 67878ff Compare July 30, 2025 18:20

k8s-ci-robot removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. labels Jul 30, 2025

mrunalp force-pushed the wg_ai_integration branch 3 times, most recently from bd25903 to a789777 Compare July 30, 2025 18:37

mrunalp commented Jul 30, 2025

View reviewed changes

mrunalp force-pushed the wg_ai_integration branch from a789777 to 6297eff Compare July 30, 2025 20:59

mrunalp force-pushed the wg_ai_integration branch from 6297eff to 4b699c9 Compare July 31, 2025 17:03

janetkuo approved these changes Jul 31, 2025

View reviewed changes

soltysh approved these changes Aug 1, 2025

View reviewed changes

k8s-ci-robot assigned soltysh Aug 1, 2025

k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 1, 2025

Add WG AI Integration

637a950

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

mrunalp force-pushed the wg_ai_integration branch from 4b699c9 to 637a950 Compare August 1, 2025 18:43

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 1, 2025

saschagrunert approved these changes Aug 1, 2025

View reviewed changes

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!

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!

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!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MikeZappa87 Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aojea Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MikeZappa87 Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

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!

soltysh commented Jul 31, 2025

Uh oh!

dims commented Jul 31, 2025

Uh oh!

ardaguclu commented Jul 31, 2025

Uh oh!

johnbelamaric commented Jul 31, 2025

Uh oh!

jpbetz commented Jul 31, 2025

Uh oh!

janetkuo left a comment

Choose a reason for hiding this comment

Uh oh!

shaneutt commented Jul 31, 2025

Uh oh!

mrunalp commented Jul 31, 2025

mrunalp commented Jul 15, 2025 •

edited

Loading

mrunalp commented Jul 15, 2025 •

edited

Loading

MikeZappa87 Aug 1, 2025 •

edited

Loading

aojea Aug 1, 2025 •

edited

Loading

MikeZappa87 Aug 1, 2025 •

edited

Loading

aojea commented Aug 1, 2025 •

edited

Loading