 Right. Hello again. Hello again. We'll give it a few minutes. Victor Morales is the lead today and he's having some connection issues. Give it a few minutes for him to join as well. Howdy folks. Hey Victor. Hello Taylor in the morning. Hi. Meeting notes are in the zoom chat. Add your name and any agenda items. Okay. It's five after the hour. So we should start. Yeah, go ahead. Let me turn my screen. Let me know if you can see it. Yes. Okay. Before I start in the, the, the meeting. If you have something to agenda, please add it. The items. So the first thing that we have is just the incoming event. This week is the open source summit. Europe. I tried to capture. The top is ready with the telcos. So those are some of the sessions that are, they're going to have it. We still have the, the, the hybrid opportunity to attend. So if you don't have the opportunity to travel there, you can take advantage of this or keep going. So I think that we have the schedule. We can take a look of the sessions to try to. Find some other topics fairly good telcos, but. If we have the, the California. So. Yeah, it's also a, but in this case, the telco is going to be just in person, right? It's only for people who are going to attend, or it is going to be recorded. In person only. Personal. Thanks. Last, but not least one summit. It's in Seattle. So. And I'm doing that week is also the. The same developer and testing forum. So. We have also the proceed to participate. It's a great opportunity. We have a lot of topics and. Fine things. Any other events. You've seen your radar and. Haven't covered. Okay. If you find something interesting. It's still free to add this. I saw events. Keep it on track. Let's jump to the PR review. Wow. I don't understand if you don't have any. Yeah. I think maybe ever, I don't know. Or it's meant over a year for sure. That's good. It's a good thing. Yeah. So. So. Well, but at least we have issues, right? So we're. We've merged that exceptions. So that'd be probably a. Some smaller updates for that exceptions. Best practice. Guidelines. That's one of them. So we start like this particular order. Yeah. Whatever you think. Okay. So this is the. Just adding the title to the sessions. Yeah. Go ahead and opening. I think. So. Wanting to get it merged. Moving on that. We didn't notice it didn't even have a title. It's just a template. Oh, this. We have other content. But I have also seen like that. Well. So. It's a good thing. That's a good thing. But the title would be nice. Or any of it. Any. Any. So this is about documenting. Any. Exceptions to following best practices. That's the main point of this. Exceptions in the, in the sense of. Of the documentation. When or in a template. Yeah. So the main point is communicated when you don't follow a best practice. So. And specifically we're talking about best practices that you could follow. You know, there's lots of them that may not be applicable. So that's not what we're talking about. It's really when you have an applicable best practice. And. You believe that you have a reason to not follow that. In the application. The operation management of an application or the implementation. Of it. And. You want to communicate that. So that's what this is about. You want to communicate that you have an exception. You're not following it. So we use that non. Don't use root processes. In your container. Is. A best practice. By that, we mean you should, you normally shouldn't use root. But if you have a reason. That you really need to use root. Then you should communicate that versus. Just doing it and not telling anyone else. I mean, it may be valid, but the point is to actually communicate it so that the. Integration team, the operations team, the security people, whoever will be able to take action based on that. Okay. We're, we're okay with your exception. Or no, we can't do it for this particular environment. But the idea is just to, I mean, I was just thinking like possible titles, but one could be like expression. That's the section, like, I mean, that's the. But in this case, it's just like, I didn't want. So what about the. This is just emitting one for one single practice. So I don't know if you are consider like, I am multiple exceptions, like multiple best practice exception on this. Or, I mean, just trying to do a brainstorming here, like what could be possible titles for, for this. And play. We prefer like we can just as all, all these options here in the, in the issue, and maybe we can both later, like, we come to help or something like that. Sure. And a tag. Ian's assigned, but we should tag him again. This was his originally. Hopefully he'll take action. Does anyone have any other, I put a title. I mean, I didn't do title pace, but I put a title or another idea. And the zoom chat. Does anyone else have. Suggestions for a title for this document. No, I think the document exceptions. The following the best practice is works for me. Can you make that a bullet list? Okay. All of her. Have any suggestions. All right. Yeah. I would just put. Up here. Yeah. Would you tag in. For what? For a given of moral sense or like for more finding. The original template. He can, he may come in and go, oh yeah, it should have had this. Or he may go, that one sounds good. If he didn't respond by next week, then we can do a PR for one of those. Yeah, I think that we should have this one. Yeah. About them. What the point of places. So, so what I have seen is, I mean, that's what we have to. So what are the suggestions for this particular case. So one is like using example solutions like more to Savannah. So where you have to predefined the network. So you for the creation of the boat, you have to specify. How many nick do you need it and all these things. And I say, I'm sorry, different in the sense that you don't have to predefined those things, especially on the fly. When the pot are created. And they have that concept. It's in endpoint and client. So which is a little more flexible than the other ones. But could be the best practice for me, I guess, like the best practice is always the first of all is not to use. The fact that I please try to define as much as possible, all the networks, not patients. And the same and abandoned supports and patients. So basically you can find your resources. Supporting both solutions. You can have a patient's and obviously what it is going to. When it is, whatever that is the point in your. You know, it's just in those. The solution that you have. For example, if you call definition, you have both like an SM and motivation. When you deploy in your. Just going to take. That service only supports one or. And that's that in the case. So I don't know if we need to discuss a little bit more. About particular topic. And then. More information or writing something. Like a draft and. And start from there. Do you have some ideas around how those practices could be tested. The only, the only way that I think it's maybe. Having a single destination. And to. To test that or to deployment as a nice, like, for example. I'm very, I'm validated. The body spirit with. Two weeks. Yeah, probably. The only. Like, like trying. First with multiple. With that. We are close with. Enable it. I'm very fine. There are two weeks there. I think it's doable. Probably. Yeah. Because of it. But that's just manipulating the. The. The Cuban. Cluster. Why, why, because you're thinking about the. The conformance test. Yeah, the, yeah, for the. Ideally any practice that we end up. Being able to document a best practice, we can also. Figure out how to include it in the CNF certification. I don't want it to be a blocker. I think that if we have enough. Ideas. We can. Information that we can write something up. Then we should do that. So if you feel. Good enough with what you're thinking then starting a draft. That can be a. Whatever you think it can. Go into a. Mark down or you can create a Google doc or whatever, maybe just link it to this. Or add it to the meeting notes, whatever you think. Then start drafting and start working on it. No worries, Tom. See you. He's gone. All right. So. We can reach out to Daniel and say, you know, if he can contribute as well. If, if you think you can get started with a draft. And then we can just keep in mind that. Ideally, we'd like to figure out how we can test. And the best practice may end up having a lot of. Various ways of testing, just like there's various ways of implementing. Which fine. Yeah, the other thing. I know. Dan was very active in the past. So now it seems to be. Mostly deprecated. I don't know what the current status of that project. So. I think that you also mentioned genius. Was another alternative. Or was. But anyway, yeah, probably. I might be. Are going to have just know the possible. The solution. Or just pick two of them or three. Okay. Yeah, I can start doing the. The draft for each. Writing ideas and then maybe we can have another call where we. Talk about. Some of the testing aspects. Just thinking about it. I know that. Part of it. The, because there's no standard way of declaring. That you would, you're open to using any of the multiplexers. And you just want to. Say, give me multiple network connections. And right now there's no standard. Way of communicating that. Then. There could be multiple implementations. So. Testing. In some ways seems like it's implementation. Specific. Anyways. If we have, if we start writing and talking about it, then maybe it'll move us closer to something that we'd like to see. I don't know what's going on with the newest. Versions of. Kubernetes where there's changes on the. The networking side, like the very newest releases that are coming out. I know that some of it's supposed to be addressing some of. The things that we've been saying, are you. Yeah, the latest stuff. From sig networking and everything. I haven't checked. Let me take a look at before. Yeah. Or. Or as part of the. Collecting information for that. Yeah, it's a good point. Yeah, maybe they did. Some. There's some change on this particular topic. Yeah. This is from. Christina. Um. It has almost a year. Oh, okay. Uh, yes, I can take that action item. To update the table of contents. The test categories in the table of contents. So you have to modify the other best practices that templates or. I mean, it's. Even older. We color is with. Uh, the best practices that we have. Or it's just something different. This is more like a. Using the capabilities of the container. I couldn't understand that last. Can you say it again? No, I was just thinking about if this is not today with the. The best practice that we have about. No name. Containers weird. This is a different thing, right? Yeah, correct. This is. This is about. Setting. Privilege equals. True for containers. Versus. Within a container having a process running as a route. Related, but not the same. And we do have a lot of documentation around this one. And we actually already have. Test. So this one would be. If we want to. Get one done soon. This is probably. One that we could knock out quickly. We have that big document with a lot of content around lease. Privilege. Yeah. I feel like there's some stuff mixed in here. That's not. The same, but. Anyways. Yeah. The name of the title is correct. The privilege flag. It's referring to in the manifest for the container. So it's just narrow. We know that the condition. In. Here, right. The only thing that attention. I mean, we, we need to draft a. A best practice or request for this one. I mean, sorry, what? No, I would just ask you for a volunteer. To continue on this. Go ahead and assign this one to me, the ticket. Are you. If you work on the draft for the networking and then maybe tag me for helping you review and help try to move that one forward. I have some time, Victor, to. Help review and stuff on this one. Yep, I can also help you on this. So do you want. We can. I think that we can both. Finest, right? Yes. Like this, right? That was the last one. I don't know. I don't know if there is any, anything else or anything that I have. Does anyone have anything else? I think I'm good. So. Thanks for attending this meeting. We will talk soon next week. Sounds good. Thanks, Victor. Thanks everyone. Bye bye. Thank you.