 Greetings. Good morning, gentlemen. Morning. And I guess we'll wait a few minutes. See. Who else joins. Good to hear from you, Jeffrey. It's good to be able to blindly attend. I've spent a little nuts lately. Yeah. But slows down. Smooths out a little bit for you. For a while. Everyone. Morning over. Meeting that's posted to the zoom chat. All right. Please add your name. Does anyone have any. Agenda items to add. Toss air gapped on there. I kind of want to know what I need to do to finish that. Like. I kind of thought it was done, but I think like. Ian had opinions at one point and I don't see them actually. Listed anywhere on what I need to change. So I'm not sure what we need to do to close that one. But I'd kind of like to get it done. Anything else. To add. So next Monday. Then is canceled. This September 5th. So. Because of Labor Day. U.S. holiday. We will. Skip that one. And the next meeting is the 12th. Open source summit coming up. We've had different people. Post some events. And I think Victor added. A few of these. I thought might be interesting to us. I think the last there was a open source slide in America. And he's posted some stuff here and. I believe he reached out to a few folks that. May. Have talks and things interesting that could come back in the working group. So. So. I'm going to be. Cube con North America. In October along with cloud native telco day. The talks are being reviewed right now. So. See what. Is on that agenda. I plan to be. At cube con and cloud native telco day. In Detroit. I plan to be there. I plan to travel. And then one summit in Seattle. In November. Also. Probably going to be at that as well. Not sure I know any yet, but. Looks like I'm good to go for telco days and cube con. Great. Excited to see you guys finally in person again. Yeah. Nice. Right now it's I'm a tentative yes for one summit. And the elephant developer and testing forum as well. We may end up having a. Tutorial at the elephant developer and testing forum on. Preparing your CNF. For certification. And going through and like. Walk through on. Using the CNF test suite and other stuff there. If that's of interest. For folks. Please pass it on. Jeffrey, maybe, you know, any of the. Books there at Dell or whatever. Matrix. Oliver. No, you all have been using it, but. Maybe we'll see all there as well. At least at the event. That's it, I think. Let's take a look at the core class. So let's say. You want to look at the air gap. Jeffrey. Yeah, I just. If you all have any. Things like I'm not 100% sure. What I need to do to actually close it out. So. I think there are some things that are more of. I would call my preference choice and grammar and language. And if you disagree and think that it's clear enough, then just keep it as is. And let's see. Do we have any. Thumbs up for you. None. All right. I apologize. I need to step away for two seconds. All right. But I think like there wasn't a past. And then it got taken down because of edits and stuff. So. All right. This is actually talking about an external thing. So that shouldn't be a blocker. It's fine that it's talking about the glossary. Oh gosh. Okay, sorry about that. I'm back. No worries. All right. So I was just trying to run through them. The very first one looks like a action item. External. I think if, if you're going to do anything, then like this talking about putting it in a CNCF glossary, if you want to do something, I would say create an issue for this action item. And otherwise there's nothing. You, and there's not much to do here. Well, I guess it's great to definition and then it go upstream. So that one's something you could look at. The next one is. I'm debating on what air gap and source and upstream. Some of those we kind of like squashed. Like I said, when I was going through the comments, there's not like, other than like some external stuff, but I kind of wanted to like finish this first before I started creating new issues is like, I don't see anything like, you know, this needs to be fixed for us to be able to. You know, be comfortable closing this PR. This one seems like something that. And might be an update versus a blocker right now. Trying to see if there's any real blockers other than right now, the only thing I'm seeing Jeffrey is maybe this definition here. Air gap environment. The rest of it seems more of. Normal discussions that happened or things that could be someone can bring back up as an update later. Another conversation here, but not a blocker. The definition that would go in a different PR, right? Like, and not only that. So, I mean, this is one of the things to you. I don't know if I agree. Like. I mean, air gap. You know, that's not like something that we came up with. Like, I mean, maybe we just find a link that we like. I mean, we put it in there, but like, I can feel like, you know, this is one of those things where we got in trouble early on, like, do we really own the definition for air gap? You know, right. I would argue, no, but isolated environment. All right. I don't say anything that's a big blocker. But in fact, I didn't realize that the air gap was at the bottom. And if you were going to add a link to something that's upstream, read more over here, that's fine. Well, I added that definition. And like I said, I think the only thing left was, you know, it wasn't like as perfect as Ian wanted it. But I haven't seen him. So I don't know, like, this thing has just been sitting there forever. And I just not quite sure what to fix. So. I'd almost rather just submit it. And if people want to tweak the definition, just put a new PR in and we'll just massage it. Yeah, I think it's good enough. There's some mine. Oliver, have you. Can you do another review or do you feel like you've from the past when you've looked at this, it's good enough that you could give a. Approval. Yeah, I can do that. But it's also just a user story, right? Like it's not a. Written in blood proposed best practice. Shall. Exactly. It's just the exact. You have a title. That's actually written there. I mean, I'd say good. Okay. In fact, I did say good. So. If it looks good to you, then please give a looks good to me. Thumbs up. You're on it. There now you're on it too. I was actually going to see if there's a startup that my friend went to. And their whole business model is doing secure Kubernetes software deployments in air-gapped environments for the DoD. So I'm kind of hoping maybe I can get them to. I mean, it's DoD, but they do kind of service providery things. Maybe we can get them to help us with some of the best practices around air-gaps since that's their bread and butter. All right. Okay. Let's go back here. So. We can come back and look later. I guess. Oh, we got several there. Thanks y'all. I don't think we updated the. We have a nice. One, two, three. I don't think that's. Did we update the number that we need? I don't believe so. I'm not going to upvote my own though. That seems kind of cheating. Yeah. You can, you can upvote it. We just wouldn't count it, right? I did great. That's what you meant to put it. Okay. Three reviewers. It still says five. Oh, that's five. Reviewers minor. We may have updated it. She's at least three viewers. Merge up for approval of three. Yeah, we did update it. All right. It's done. Thanks, Jeffrey. Yeah, no problem. Sorry, it took so long. Hey, we're going to get going now. Okay. Let's see here at f5. Right. What's going on? Why is this merged? Yeah, this is just a, I don't think that these. This is one of the minor changes. That we can do without having as many. Full request latest template. We can use existing best practices. Change the interest. Fix some learning issues. All right. Let's see what we're doing. What list? Okay. Word list. Workload. Context. You haven't been making completely optional. Or is that optional? All right. Trade offs constraints. This is matching up to how we've been doing things. Yeah. I'm okay with it. Same workload context. Just proposal. No, it's constraints. Let's see what he did. Oh, he didn't fix the title. Workload context. All right. I'm good with this. What about y'all? Works for me. I'll go in and. Bless it. Oliver. What do you think? Good improvement. What do y'all think? I'm looking at it now. All right. My question. Oh, I guess I can put more people on this. That's good to me. Why does mine say fix things? I didn't request. I must hit the wrong button. Oh, I did. I feel like they may have swapped this. I defaulted. Go to the bottom. No, I don't think they did. All right. That's it. We made it through there. All of the poor quest. It's clear. All right. Anything else for today? It's time to get some new best practices. And we can talk about that. Next time. Yeah, sounds good. I'd like to. Set up some working sessions and let's just start. Idea and like writing some of them out. Sounds great. All right. Have a great Monday, everyone. Yeah, have a good one. Cheers. All right. Have a great Monday, everyone. Yeah. Have a good one. Cheers. All right.