 Good morning. Good morning. Good morning. I'll give everybody a few more minutes to be able to come on in. Just give it a minute or so for people to be able to come on in. And I'm actually kind of hoping for the network folks to be able to come in because they're actually kicking us off today. So, good fun. Alright, we are at five after I have given the lead poke. And we'll, if we need to come back to network, we'll do that too. So good morning. You have made it to the TOC meeting. Our normal antitrust supplies. I'm your host this morning as Liz is out of the office today. So, yep, you've made it here. Our normal planning doc in here and that's where we're tracking attendance. So to see members are tracked over in there. Today we've actually got a few updates from some folks. We've got tag network tag observability may or may not be here, but I left the slides in here. We've got run time security storage and then go through a quick review of anything kind of outstanding for projects, wanting to move levels. Happy to take questions as well. And I can keep an eye on chat so good fun. All right, hearing no direct objections. I will walk us over in towards tag network. And I'm not sure if I've got anybody on the line for network. Hello. Hello, you are here. Welcome. Oh my goodness. I just joined and then I heard network. All right, perfect. You are kicking us off like just in time development. Go ahead. Just as I planned it. My hair brush and everything. So great. So all right, some updates since last we met. So there's a project that's interested in presenting for consideration for sandbox it's called fab edge. They will be presenting in this Thursday. So in a couple of days. We just a small note for those that do attend the tag network meeting. We did adjust the time to two hours earlier in the day. So it's the first and third Thursdays of the month. But now at 9am Pacific. That just helps us with some earlier time zones. So fab edge will present. We went ahead and got locked in for some office hours. A cube con EU. I think since last we met, we had a cancellation of the meeting but we did have a meeting last week and another one this week, we've been consolidating some of the, some of the interrelated projects between tag network. Service mesh working group service mesh performance and, and then compacting that agenda, which has been nice with there been, we had three times as many butts in the seats at our last meeting. Intel red hat Google all showing up and some others. Or folks from those those places so so since last we met there was. There's an upcoming service mesh users survey very short survey to go out but work collectively excited about that. That would come out from the scenes yet. There was a body of work that was previously mentioned on this call within the service mesh performance. A paper and article to go out in IEEE publication, and I just checked and I think I think it's out. So there's a link to it there. That's the other piece of news and then the last piece of news is there's a load generator nighthawk. There's a presentation from a Googler one of the main, the maintainers of nighthawk on their adaptive load controller. So it's a great, great presentation. I think there'll be a demo of that load controller. At this week's meeting so that's the question for you. That's the new stuff. And then, Mr Fitzgerald, the, let me send you a link to, there's a Google doc that I think I has like seven questions or so to in the survey. It hasn't gone out yet, but feedback that you might have on whether or not those questions are appropriate or some are missing or would be good. So I'll put a drop a link in chat. Perfect. Thank you. Other questions. And yeah, one note about like the their their meeting time has moved up you are now at a 9am Pacific, which hopefully should get more folks for you. Less complaints, maybe. To be fair, like 11am Pacific is kind of late for being able to pull off like everything. So, yeah. But apologies to Asia Pacific. There's, there's just no good time. So anything else that you wanted to cover Lee. There's just some outstanding calls for participation on there's an initiative around service mesh patterns. So there's there's some that are being written identified and written up. There's a new GitHub organization that is dedicated to just that initiative. And we might invite it's well we haven't got him on the schedule yet but but we should be inviting a few folks from some of the Kubernetes network related initiatives or network related six like API gateway. There's something of a, I think it's somewhere in multi cluster there's kind of a service catalog. There's a working initiative and so a lot of that is very relevant and interesting to the working group initiatives here and so we'll look to try to elevate and cross pollinate. So actually if there is our folks in the call that that represent those initiatives are involved in those initiatives in Kubernetes, please reach out, we'd love to get people in the schedule. Thank you more. Thank you network. You made it just in time. Well done. Run time I'll pass to you. I know you're here. Hi, yeah, even works to go ahead. Yeah so a few updates in terms of projects and presentations. In our meetings in the run times and container space. We actually reached out to this project call call in clover containers that it's take on confidential computing from the folks at Alibaba. And we expect them to present pretty soon. They're not on the calendar yet but they're, they're, they are in the CNCF sandbox already so they're very interested in engaging. Key is another project that will have a presentation on November 4th, Thursday, and this is a container runtime in rust. So it's a different take on something like run C but written in rust. Then on the workloads space, a couple of projects, we have direct teeth. We had a presentation in our last meeting in this project basically allows users to perform orchestration of server less workloads on top of supply Kubernetes using K native. And then another project is Armada, and we'll have this project presented on November, November 18, and this allows you to run Kubernetes jobs on multi cluster environments. There's another project called K Armada, which is very similar to this. So this is a kind of like a different take on running jobs on multi cluster environment. Then on the machine learning ops or MLOB space and edge. K0S not to be confused with K3S is another Kubernetes distribution for the edge or to run workloads at the edge. And we'll have this tentatively on December 2, which is next month, first meeting on next month. And finally on the activities in the tag. We've finally decided what our logo is so you can see that the upper right corner. So it's going to be like a cheetah with, I guess, some lines that it looks like it's running fast. And thank you. Thank you for helping now with this. And a couple of working groups in progress that we were talking, talking to some folks about this and hopefully we have a charter for some of these web assembly and edge, a lot of interest in this area, or in these new spaces. In China, KubeCon, we have a session scheduled for the tag and, you know, hopefully we get some more engagement with that session. And yeah, that's all of the updates for tag runtime. Happy to take any questions. Thank you. Yay for new logo and yay for being able to have lots of things scheduled so looking good. Any questions from folks. Yes, congratulations. I'm like, hooray logo, logo looks great. All right. Security, you know, security folks are here. Hello. Hello, come on in. All right, so just a quick update. We have the community nominations for tech leads. We talked about this a little bit the last time, basically, community members can vote for who they want to be tech leads. You do all the ongoing business of KubeCon decided to extend the deadline two weeks. So we're opening up until November 13. So a quick update on security assessments. We have cloud custodian that's really graphic up and coming to conclusion. The PR should be merged within the next one or two weeks. We are starting the ago security assessment. We are looking for one or two more reviewers. So if anyone's interested, they can check it out. And we have two projects in the review queue currently captain of the several projects that are looking for incubation. Upcoming also we are jumping the trails for cloud native security map, which is the V2 or cloud native security map. And this is basically providing a way for folks to navigate the white paper to say if you're interested in a particular topic here. Here are some sections that you should look at and you hear how the sections are related to go for example, you know, runtime protection or supply chain security. And finally, the last update is we have the supply chain reference architecture. And we have defined what the reference architecture will look like and this document will be available for public command in the coming week. And that's all for our update this month. No, thank you. Any questions for the security folks. We can move on I know storage has a lot going on so come on in storage. Hello. Hello. I've set the bar high. So, there are, there are some projects which are going through, which are going through the process. Longhorn is in the voting stage. So, you know, two power first is just being finalized. There's, there's a handful of small things on the, on the due diligence doc that need to be finalized and we're just getting the list of repose and licenses finalize Open EBS is on pause, we do have, we do have some questions, which the project has some questions which still needs to liaise with CNCF legal in terms of, you know, there are some pretty simple binary yes no questions that need to be answered in terms of things like trademarks and stuff like that. But we also would like to spend some time with that with, you know, saw the rare and run through a few a few options and questions that came up after our discussion with the team the other week. And we're going to be presenting at the CNCF China and covering off, you know, some of the new documents that we had written including the cloud native disaster recovery and the performance white paper. And some of the things we'd like to, we'd like to, as a mask of the to see is, as the year is coming to an end, some of the sort of large big ticket items in terms of you know docs and things like that that we were working on are coming to a natural close and we've been, we've been working on some of the plans and some of the options of what to do next, including, you know, trying to figure out which projects or which areas to focus on and maybe you know specific problems or challenges that we think might be might be useful, either from an end user point of view or from a to see point of view. So, so we'd love to, we'd love to get would love to invite people like maybe side Aaron and whoever else from the to see would would be interested to join our next call and help us with preparing a plan that we can kind of launch in in in January for, you know, either new content or or or new projects or or things that we should be looking at to give us a bit of a focus. I see side has, has just said that you'll do that so I'll, I'll extend the invite but we'd love to, we'd love to see you at our next school. It's the second Wednesday. So yes, November 10. Make sure like my looking at a calendar right and like that is a Wednesday November 10 meeting. Okay. And that's it for us. Okay. Yeah, I'm not sure if anybody wants to be able to like give advice here directly. So hold for a moment. All right, seeing nobody on mute. We'll save that for like a November 10 meeting. And we can do a quick run through of everybody who is applying to move levels. Please correct me if things have changed for any of your projects folks that are currently accurate. I know that we've got open metrics long horn dapper currently in voting. So, all right seeing no comments seeing nothing come up around this one. Moving to questions anything else that people wanted to be able to cover today. Ricardo, go ahead. I was just going to say it's a quiet meeting. I understand that like many, many people are out of the office this time around. So, yeah, yeah, I skipped observability because y'all didn't have any substantive updates, which is fine. Yeah, I could speak to a few things over briefly we've had a really quiet week to there was a lot of lead up to coupon coupon was awesome. We'll have I believe it's working on a blog summarizing some of the observability content that happened in LA. We gave our talk as well, when I think was received. And in the coming weeks, you'll see a lot of PR activity in various to see and or see up related repose. There's a couple things that now that we're past coupon and the dust has settled. I would like to move forward on immediately. One is kind of is it sort of a segue from the last to see meeting around and user community radars and wanting to map vendors and projects and technologies and adoption and things like that. In the observability space we have a whole pile of all of the above. So, we're going to just build out in the coming week or so just start with a list and really make a graph. If you will database of who's who to maybe prototype out something that might work more broadly, but for now we'll do it first for observability and see where we get in a few weeks. And that's pretty much it sounds good. Thanks for the update. Good. Okay. All right. Last call for questions for this really, really quiet group. All right, with that I will send everyone back into their days it's good to see all of you. Go, go do things. All right, thanks.