 Greetings. Hello. Hello. I have put your agenda item at the end because I wasn't sure how many tags we were going to get today. How many. Oh, right. Okay. Yeah. Yes. Yes. Most of them. But you know, we'll see. The only one I'm currently missing is the contributor strategy folk, which kind of makes a lot of sense. They're kind of our most American focused group. And everyone was out yesterday as far as the Americans go. Yeah, I hope everyone had a good long weekend if you have to give people a couple of minutes to join 1615. Oh, no, we lost one coming back again. Dropping in and out. Yeah, kind of inclined to be able to hold for app delivery because they kind of kick us off first. But yeah, we'll see it could be late day. I see people piling in now. Yeah. The trouble is every time we start five minutes late, I think it gives people like an excuse to think, oh, you know, it always starts five minutes late. It does always start five minutes late. Yes. Okay, today we'll start four minutes past and we'll work back minute by minute for me. Well, we've got a question in the chat. Amy, where would one find the time of day for the meetings that occur on the third Tuesday of the month. It's the same time. It'll be on the CNCF public calendar. Give me a second and I will drop a link in for you. Great. Thank you. I just recently started joining to take some notes on behalf of tech security and I thought I joined at the right time the third Tuesday of last month but it was as if I was like an hour late. So I just want to make sure I wasn't out to lunch. All good. Go ahead and take a look over on that calendar, but at the same time first and third there stays. Welcome. Thank you. We seem to have a reasonable turnout. So maybe we should get started. So welcome everyone. And trust meeting logistics. And I'm sure Amy is working out who's made it today. Mostly today we're going to be doing status updates from the tags and hopefully also from the TOC. So do we have tag at delivery with us. If not, we can always. The only one here is me. So currently we are reviewing that before incubation. So we are going over the, oh, sorry. This is already there. No, no, this is perfect. Go ahead. No, you are responsible. I'm not here. It's nice to hear some different voices have some different participants. Yes, but as I was getting away, I don't know what I did. Yeah, maybe on the projects and I jump quickly and then that Thomas jumping us on the operator white paper. So project crossplane I think it's with the to see right now for review we talked to Harry as the to see is on about this one. That per incubation donation is going on under review they have prepared the due diligence document. We also want them to present. And the, I think there's some open questions that we will bring up in on under that per review. Because it's kind of like a different project in what it's doing and how it fits in, but we will keep you posted but we definitely want them to present to the tag first. Thomas you can talk about your not your like your personal but the operator white paper. Okay, so we were very proud to to can announce that the operator white papers finished. So currently we are trying to make it a bit more pretty waiting for the PDF and afterwards we can publish it. So pretty cool thing. The thing is that the work on the chaos engineer might be worked on. So I think they have kind of a job and so on. But I think I was already knows more about this. And they are in the early stages of there is a charter document team, the security team is now joining in as well providing some of their input. So just got input here. So security is it. That security story. Yeah, yeah. Yeah, security to your feedback we have like the networking app delivery and security data gather that's also why we're trying to put this into like this. Working group mode but with cube can reviews and everything and everybody being super busy this moved a bit slower than it was initially supposed to boot it. But the good thing is we are moving in the right direction it just takes us a bit longer and all the necessary. People from all the texts are already involved in there. Great, and I can see quite a few participants in that chaos engineering working group charter. So, I'm guessing if anyone else is interested in getting involved they can reach out to tag up delivery. Yes, reach out to us. And presumably the same is true for that cooperative delivery. Yeah, this is the one that changed its name it was called an application enablement working group. We were not super happy with that name. And we came up with cooperative delivery and some people might still not be happy with it I think the content of look at the charter is still valuable but we're still struggling a bit with the name. Not really about how like we can build more pluggable interoperable assemble application and infrastructure level applications together like problems. I think everybody when one who reads it is clear about the problem statement that you might have your manifest available but then you have a cluster configuration and then somewhere in between you figure out that those two things do not fit together when they go to a cluster because certain things are not working out or different projects handle different aspects but not everything in full to ship something. So this is something we're still iterating on a bit and also everybody is more than welcome obviously to give the chart their reason we want to be very clear on the problem statement and there are amazing drawings in there done by Alex Jones who's always doing amazing And also if you have ideas for better names please feel free to come up with a better name so we all understand the problem we want to solve but we can't give it a nice and clear or perfectly clear name yet. But the problem is there in the use case I really driven from end user companies to say this is hard just that right once deploy everywhere is not working as it's supposed to be and there are dependencies in there that we have a hard time modeling or bringing together. I can see from the draft working group charter there's I don't know 1520 different name suggestions in there so clearly that's. We're in a difficult for naming is hard. This this one is when naming is really hard but again invite everybody to have a read what the problem with trying to solve I think lots of people will create the problem, just the naming of that thing that we're trying to do here is a bit hard. Sounds good. Okay, any questions for delivery from anyone. Okay. Thank you very much, both of you. Um, okay tag network then. Hello. Good morning. Fairly quick today I think so a number of project updates. Since last well geez I don't know. You know what, I can't remember what happened since last we met, but I will say that there been there are a number of a few projects under current review so if you train your eyes to the left hand side, the middle set of bullets on psyllium is under review for incubation and it's going through diligence. Linkard is also up for graduation and I believe it's in public comment as of now but we'll hear more about both of those I think toward the latter part of the call. Yark was recently reviewed for consideration in sandbox. And a couple of other projects were also recently reviewed for consideration in sandbox. Mashery and service mesh performance. And I think it was those three with inclusive of YARP that were just reviewed. There's also not listed here but but just just coming notes to me as a few minutes ago. Chaos mash is also proposed for incubation so it should be a third bullet point under projects under review. And so it Calvin if you're on the phone. You guys are on the agenda for presentation next, next time we meet so. I mean, you all. I grew up I grew up in the Midwest so it's like that's just have a good Calvin you're on and good, we'll keep you up nice and you know Calvin we should probably make consideration for the fact that we should. And Amy has facilitated this in the past has been great but we should probably find an earlier a couple hours earlier. It's pretty torturous time for you all. Thank you. Thanks for being so thoughtful. We need good good. We need to, in general work on our the timings of the, the working groups, the working group meetings and signal work meetings anyway and so this is a good, a good catalyst for us to do that. So, so Liz and Dave, who are both on the TOC liaisons for tag network have been supportive in trying to ensure that we've got enough tech leads enough co chairs that to help steward tag network and so that been kind of an action item that we've been working on for a while and Ed Warnke is an individual that's been active in the tag for quite some long time has been focused in this general networking area for quite some time he's a, I'm going to get his particular the nuance of this particular wrong at Cisco but he said, distinguished services engineer, the distinguished engineer with some other qualification in there anyway, he is shortly to be nominated for co chair for for consideration for review from all of you. So we'll say more about Ed and who he is in his focus in that nomination, but some of you already know Ed so. And it can with that part of the focus is to well live and up a little bit of what we're doing, like we are intentionally within the charter we're intention trying to liaise with other group with the projects within the tag, but also and so getting from them on occasion maybe once a year is like something that would be ideal if they were just even to present their annual review might be quite nice. It also is the case that Kubernetes sig network has any number of things going on that, like the gateway API spec is is comes to mind immediately but it's been a long time since we've invited them to kind of present that the latest activities to cross pollinate and so hopefully with the help of potentially a new co chair. We'll get more activities going in that regard. And that's the yeah that's the deal. That's the update. Sounds fantastic. Any questions for Lee from anyone. And good to see some more people coming into leadership roles as well. Excellent. All right, who's next. Have you got observability or is that am I looking in the wrong. You were looking the right thing. Okay, too fast. Observability is up. I hope we've got someone here from them. I'm going to take that first but it's suggesting maybe they're not here. I'm not a official representation. I'm afraid, but Richie had mentioned that he's has an internal conflict unfortunately that came at last minute. So, I actually can't speak to everything. Of course that the six been up to, but there's, I think like it's pretty exciting to see the observability white paper. I think it's going to come to a close with with news that picking it up obviously, and yeah, I think there's a lot of exciting upcoming things happening. That willing to talk a little bit to what I know that it's happening in the area but I mean, I think that folks have already put together a lot of the information in the slide and it's probably not worth me talking through the any more points and what's going on. So yeah, Richie sends his apologies. Okay. Thank you for stepping in Rob. And welcome. So the observability white paper where it says close to done and the new stack is picking up as a reference does that. Does it need a kind of review cycle. I'm just sort of hesitating on the new stack going to say yeah this is the CNCS statement question. So it's had a lot of internal review in terms of reviewing with other CNCS members. I think that obviously with the single very open to doing that. I'm not 100% certain on the status of that but I can get Richie to follow up and make sure that's happening. Thank you. Yeah, it'd be great to send it around on the TSE mailing list and just make sure there isn't a. Well, yeah, make sure everybody's on board. Yeah wonderful yeah well we'll send it around to the mailing list and make sure any further reviews that need to happen happen. Fantastic thank you. And actually just going back one one more question do you happen to know what the is options. I'm wondering what the status of that is is that applying to be part of CNCF or was that more of an ecosystem presentation. I believe that was a presentation. But yeah we can. I don't believe at this time there and looking to submit a project but yeah I can definitely follow up on that as well. That's fair it was just a clarification, I think it's great if we're hearing from an exploring projects even if they're not necessarily part of the CNCF it's all part of the broader ecosystem so it's all good. All right. Any questions for tag observability. Okay, was it who is next. Run time run time. Hey, everyone. So some days for tag runtime so as far as our presentations and projects in the workload and orchestration space, we had a presentation from cater for incubation. And the projects already in their public comment period. And it's open for another week. So if you have any comments. Feel free to post them on the document or on the mailing list and we did actually posted some review comments. And I, we think it's in good state for incubation but hopefully other people have some feedback. Another project that presented was K armata, and this is multi cluster Kubernetes and multi cloud environment for Kubernetes and in. Basically, this is a project that it's a continuation of Federation be one and be two. So, pretty excited for those people trying to run Kubernetes and in multi cloud environments. I don't know yet if they're applying for sandbox so I'm checking with maintainers so hopefully will they'll be interested in applying for the CNCF sandbox. Or incubation or whatever, you know, they would like to do. In the containers in runtime space, we reached out to a project called Yuki. And this is a container runtime and rust. I think there's another one that presented a few weeks ago but this is another take on the container run times in rust. And hopefully we'll have them present. In last but not least in the ML Ops. AI edge space. We had the tfx project present. This is an end to end machine learning. Kind of like you flow as a project from Google. Pretty good engagement from Dan, you know, as far as telling us what the project is about. Super edge is another project in the edge computing space and they presented in our last meeting and they're, they're actually applied for sandbox. So this is another take on edge computing like cube edge or open yurt. So they have some similarities but also a slightly different take as they're applying for sandbox. ML flow. We reached out to some members so hopefully we'll have a presentation from them. And Yeah, so this is and also end to end machine learning from similar to cute flow and tfx and K zero as is another Kubernetes distribution for the edge, kind of like K 3S so we'll we also reached out to them and we expect them to have present sometime soon. And as far as tag runtime activity. Oh, sorry, and then my ML Ops space and there's another project called cube DL that apply for it's not listed here but they apply for sandbox and they got accepted so that falls within the scope of the tag, which is machine cube DL is cube deep learning so isn't that machine learning type of space. And as far as the tag runtime activities. So, we are planning or we submitted a cube con North America sessions we plan to have some updates there and hopefully we'll have somebody present in person. If it'll, if it's possible. We're also engaging this other community call the ML Ops community. So hopefully we'll have some collaboration together with them. So some of the projects in the ML Ops space. You know, are also engaged with this community so this will help drive more interests and projects, you know, and in the tag. And finally, we have Evan Lazar taking over some of the work that Renault Renault had been making in the container orchestrating working group container orchestrated device working group. So he's moving on to some other working at NVIDIA so even will be taken over that. And yeah, that's all the updates. Happy to take any questions. Any questions from anyone. All right, thank you for the update seems like lots going on in the world of runtime. And ML Ops in particular machine learning. Yeah. Yep. Hello, everyone. Hey, Emily. So we have a few updates today. We're going through some security reviews for closing out build packs and we'll be kicking off cloud custodian it's actually currently underway right now. So nice to see some progress there. Cloud native security con is happening again this year previously named today, we're now trying to extend the cloud native security events into more of a con. So expect to see a lot more in this space coming soon. CFP is currently active closed July 25, please retweet get the word out. This is going to be a hybrid event. It will still feature capture the flag. And we're also exploring whether or not we can pursue a security village and the main vendor area. We've also done some work on our general governance. We've made a chair transition checklist so for those that are interested and would like to check it out. Feel free. There's the link and security pals is going well. And some of note Kyverno was engaged with security tag through the security pals program and now they're going to be providing presentation tomorrow so if you're interested, check it out. Amazing. Any questions for Emily. Thank you for the comment. I really like the chair transition checklist, but because when we had like the new co chair voting. This was kind of like a gray zone to some extent for how did transition and everything happens to great that this is available. Thanks. It's made it a lot easier for us to be able to bring in new chairs and understand everything that we've done to date. So I'm happy to know that other groups are finding it useful. Amy, I wonder if we should put a reference to this from like the general tag documentation so that other tags can find it. Yeah, no issue with that. I can drop in a PR for this as I get to clean up the repo this week so all good. Thank you Amy. Sure. Okay. Storage. Hello Alex. So, um, so we have a couple of projects going through incubation. The Longhorn project is proceeding well. And we recently concluded the survey from the end users. So hopefully we'll have the document in drafts to share with the sponsor. And the FES has sponsored and the DD doc has already been drafted and we're meeting the team to to review that this week and open EPS. We're looking to meet the team hopefully next week to decide on on or to work through what they need to do to make some changes to help with their incubation process. Hopefully we'll be able to move that forward as well. The big news is the cloud native disaster recovery. We've we've spent a number of months working on a document which we're really really has taken a really good form now. The primary author there is Rafael Espazoli, who joins tag storage as a tech lead recently. And, you know, if you think naming things in terminology is complicated. Yeah, cloud native disaster recovery is a minefield. But I think we've tried to capture all the all the important bits. And I would like to submit this and actually ask if it's the right thing to do but but I'd like to submit this to the to see mailing list and and and open it up for for for further discussion and any other feedback so that we can formalize it and turn this into potentially a formal cloud native. So we'll see and see if documents is possible. And now that we've, we've sort of completed the majority of this effort on this document will will look to circle back and try and finish off the performance and benchmarking white paper as well. Which was sort of the prioritized for the VR document. Great lots of activity here as well. It's been exciting. Yeah. Definitely sounds like a good document to circulate. Lots of people will love to see that. Any questions from anyone for tag storage. Hey, did we get any but I think we skipped over contributor strategy. I believe they're out today. They're out today. Okay. Have we missed anyone or is that everyone. That is all that we have we are now over into the project incubation and graduation sponsors we've talked a lot about some of them running around. So. Yeah, so maybe we can just get a quick update. Oh, Shane, Shane, you go first. If you've got anyone give us quick update on the ones you're looking at. Okay, sorry. So just really just virtual cooblet and, and, and actually this is going to be a much longer conversation. The issue is virtual cooblet doesn't pass the conformance test. You know, it's just, it's, it's obvious we all know it's kind of an approximation of what the, what the real cooblet is supposed to do. And, and, and, and I think there's just been a lot of debate about even within the, the, the virtual cooblet team exactly about it. Exactly what the situation is how much, what percentage of the conformance test, they should be able to pass or whether that's even reasonable so I actually missed the meeting I was on vacation. They had a meeting a week ago to discuss this and I intend to follow up with them shortly. Okay. And now I'll reach out to the, to the technical experts in that area and then get a, get a read on it and I'll report back. Okay. Thanks for the update, Shane. All right. Elena, are you here. Elena is actually in a conflicting meeting but she's let me know that open metrics currently has some kind of open questions but open telemetry is actually ready to be called for a vote. Okay, good. Right. So open metrics is still out for public comments. Right. Okay. I'm just in here. Also struck in a separate meeting because that Monday thing collides into Tuesdays so. Oh, gosh, yeah, right. No updates from him on in total or on psyllium right now. Okay. So Kada, so Kada incubation due diligence document is out for public comment. I think that was already mentioned. It's got about a week left, if you have any comments to make. Saad are you with us. Nope. And Lee is also separately not with us so this is going to be kind of short. Okay. So I would like to recommend rubling onto Ricardo. Yeah. Yeah, I think for crossplane we are ready to open public comment. This should happen very soon. And for cloud custodian I need to sync again we had a call a couple of weeks ago. And we wanted to sync to start due diligence. So it should happen quite soon. All right, thank you. And Davis Dave here. No, but David made a note to me saying link linker day is pretty much ready to be called for a vote so. All right. Good stuff. Well thank you everyone who was here and was able to give updates. Any questions or any other business anyone would like to raise seems like. There's a quick note in chat from lead it says psyllium is still like moving through and all good things there. Oh yeah. Good. Okay, unless anyone has any other business they can write in about the next 10 seconds, I think we'll call it a day. And yeah, enjoy the rest of your week everyone. All right. Thanks. Bye.