 Okay, so we're winging it today. I will kick it off for topics that folks have that they intended to raise today, but may not be on a written down agenda quite yet. And I will, while that is happening, look for a couple of PRs I know went out for added conformance tests since our last meeting. Anybody have topics to raise silence? All right, seems like this might be a quick one. One, I know off the top of my head there was a watch conformance test added in API machinery. That one is particularly interesting. And I will send a note if I can't pull it up quickly here. But that is essentially to ensure that the watch, asynchronous watch works in the conformance test suite. And are there others that went in in the last couple of few weeks that folks are aware of? Mostly I just wanna make sure there are no surprises. So I wanna over communicate on what is added to the conformance test suite. There are mechanisms for you to self discover that, but this is just another mechanism for doing that. In other lands, before our next meeting, I believe we will have a feature complete for 112. And our agreement at the conference working group meeting in Copenhagen was that we would make an effort to have a better plan for what conformance tests were intended to be added in 112 by the feature gate, which is an existing gate we can add to rather than creating a new process timeline. So I would encourage folks if you intend to work on conformance tests to collaborate on that effort and Aish or Mitra will send out some more communication on that in the next few weeks, I think. I think the only PSA I have is that we typically lag release cycle for doing Sonobui updates just because that's what happens. So we might have a release around Julyish timeframe. There was also a separate request for me to do an update for the instructions. So I might do a PR against the CNCF conformance repo around that time to update instructions. I've got a few slides or updates from Aish as well and had one of the get some thoughts on some of the API's new direction that we're taking. I was looking at the conformance working group area and the notes, are we making a new section or the meeting minutes? Feel free to make a new section and add that. All right, I'll do that real quick. So updates from Aish and API Snoop update. I'm gonna go ahead and try to share my screen with API Snoop slides. Are you able to see my slides? Not yet. I think so, unless it's just a black slide with no text on it. No, that's not the one. I've been having some issues with my screen sharing. Let me try. I think you're equal in this laptop. Try again, share screen. Sometimes if I reshare it'll show up. I'll drop the link into the channel and maybe someone else can try to move the slides. I'm gonna drop this in for everyone. Just progress through it, if that's all right. Sounds great. All right. Aish is actually updating this live, so thanks for that. She's at a conference internal to Google so they've got lots of watch tests that were added. There's a PR for that. It's on slide two. There's also some ADE aggregator tests where they're waiting for some review there but they're in scope for 112. And there's a conformance guidance PR. It's almost ready. And the link is there on that slide. On slide three. There was two main groups that I think she was working with ABA Machinery and the note within API Machinery. This is the list of the ADE tests that they were able to promote. They've also got a tracker sheet for that. She's gonna be working with the vendors in particular to make sure the flakiness improves and they're not skipping particular providers. And they're about to do some promote these cases via PRs for API Machinery SIG before looping in with the SIG architecture. I just actually editing the slides, hopefully it's getting there. The link is restricted, so. Sorry, that's not useful. Okay, I'm just giving you that feedback so you might give more context than you would otherwise if you think people are following along. Sure, sure, I appreciate that. Anyone, I'm gonna update it so it's public. All right, I've re-updated that. There's some improvements for the POT APIs. That's, I'm gonna focus both for API snoop and for age. SIG node, they've identified a list of APIs inside client Kubernetes Go to focus on for 112. There's a link there to that particular issue. This is on slide four. She's been working with us to correlate the ETE test to the API calls that they make. It's helping particularly in SIG node to be able to see which endpoints are already covered but the tests aren't promoted. We're looking to try to provide a matrix for each of the endpoints to all of the tests. We have an initial dump right now inside ETE correlate. See if I can drop that into the chat real quick. So there are the initial outputs. If you run, if you look at that file, it's sorted by the API calls per ETE test so that you can see for each ETE test, here's the list of all of the endpoints that it hits and the sorted by the number of times they hit it. Where ICE is also working closely with the Globont vendors to understand what they're doing, particularly at how different API and verb combinations are being exercised. And moving a bit into the POT API spec it's a little bit different than just the ETE test and so we're digging in a bit further to see how we can include that in API stoop as well to see which of those are worth promoting. I'm still a bit unsure how we look at ETE test and conformance with regards to POT API spec but the initial findings are in a link here and I'll drop that in the channel. I think this may have to request permission for that one. And for next steps, they're gonna do an API analysis for the API verb combination and take the results to signal we'll be doing something similar within API stoop going beyond just the simple dump of the correlate we have and hopefully be getting something on the web. That looks nice. With an API stoop we've got a couple of open tickets and that might be of interest. I'm gonna drop our issues link in here. One of the things we're looking into right now is trying to augment client go so that every time any application uses client go to connect that we could somehow correlate that call to an entry in the audit log which provides some really interesting data to analyze for all applications instead of we are currently working to do it within just within the ETE test space. And that's been some interesting things. We also updated the API stoop. So if you look at apisnoop.cncf.io it's working but it's kind of a mock up of where we think things should go in the future. I'll drop that link as well. If you look at the web portion the data portion is not there yet. This is where we're talking about having the actual data for each API call in a bit more in depth and possibly within the ring when you see a particular API call being able to click on it and seeing all the ETE tests that hit that particular API call and possibly all the applications at some point including all of the data that flows through it so we can get a better visualization for how we're using our API. There's also been some work on the capture to make that easier. I think that's another ticket where we were looking at using advanced audit web hooks. No, that's not it. Yes, using admission web hooks as an alternative to audit logs. Yes, audit logs are where we will go and be long term and there is that cap. If you haven't seen it to add support for audit logs to be added dynamically but right now this might be useful to get us a good way there as far as the call itself. We won't get the results. We won't get some of the other data that's there but I'd love some feedback on all of these different components as everybody has. Yeah, I'd just be really valuable. I think that's it. Thanks for both for being a proxy for the update from Ayesha on that stuff and for the API Snoop. I followed a few at just haphazardly as I look at activity in the Kubernetes repository that the feedback that you're giving on audit logging is actually driving that feature in a more useful direction. So that's a lot of appreciation is due there. Thank you. I'm stressed. Thank you for that feedback. Others have questions or comments on update? Just in time slides passed off to someone else to present that was a takes a village. I didn't realize that was a fully community ever right there. Okay, anyone else have any PSAs or updates or questions or comments? Otherwise, rather than continuing an open discussion, I would suggest we call it and come back together with a better agenda the next time around. All in favor say aye. Aye-aye. Thanks, Michael. All those say nay. And we all have it. All right, thanks guys. Bye. Take care. Cheers. Thanks.