 Okay. So I think we've waited long enough. So let's go ahead and get started. So our first item on the agenda is agenda bashing. So is there anything that anyone would like to discuss that is not on the agenda? I sort of stealthily added to the agenda under events. If we wanted to ask if it's okay to send our invites for the meeting to sing networking. I know that there was some comment last week where there was some confusion from the travel pink guys where they sort of said, Hey, you know, we wish you guys would have sent this to the main thing networking list like everyone else does. Then we know that meeting was here. And then I know Sergey wasn't aware of the meeting. So do we want to consider politely asking. If that's the way that they want us to communicate, then yes, by all means. It seems to be how it's done, but I'm always one before sending something that's going to span people's calendar to sort of ask the list and say, Hey, is this actually an okay thing? Yeah, I mean, if we're not sure, I mean, one of the things we could do is just ask Tim what the proper etiquette is in this scenario, and before we spam a bunch of people. Yeah, I'll go ahead and do I can take an eye to do that if that's what you'd like. Yeah, let's let's go ahead and do that and then just to that way the word we're not coming off is too aggressive. Yeah, and if that's the way that he says, yeah, add it to that, then, you know, by all means. Cool. And add basically I figure out what was the problem. It appeared that this meeting invite went into the Google calendar so I now have to check outlook calendar Mac calendar and then Google calendar, you know, too many calendars. This is another good reason to see if it's okay to send it to the, the list. So, I feel your pain there. Okay, so is there anything else so we like to add to the agenda or I would like to add ask one thing. Looking at it, there's no real getting started. You know, how, how would I go and create a new plugin for network service mesh. Yeah, we, we haven't quite gotten to that part quite yet. We're close right. But it's it's still it's still useful feedback because it tells us number one that it is something that we need to do and to that there's people are interested in it now. So, yes, yes, because I was not hacking something. I'm kind of looking at it trying to figure out where just where to start. Yeah, and we're going to we're going to talk a little bit about the last year Frederick you went on mute. Sorry about that. Yeah, so we are going to talk a little bit about where we're at as well and you'll get a sense as to where like we've done work that will support us in that area. Yeah, I mean, just, you know, starting a wiki and starting just typing a few hints and then, you know, people working on it, we can ask questions like I don't understand and iterate through it. That's a really good point. I mean, ease of entry into doing development work is a huge deal and we want to be as friendly and easy in that regard as we can. Yeah, I completely agree and the easier we are to to understand the architecture for newcomers to understand not only means that people get to work faster on it but also means that our architecture remains simple, which means less bugs and ideally more more potentially more flexibility with the type of projects can they can handle so yeah I completely completely agree so this, you know, and any any help that can be given that area as well as is definitely highly highly appreciated, you know, as especially, especially if you're looking at this from a person who's who's new to the to the code base. So, okay, so is there anything else that that we should add in looks like a pretty packed agenda. Act agendas are good. Yeah, exactly. Yeah, there's a lot of good stuff today. So, so first, let's talk about that is talk about the results from the cumulative dot voting poll. So, is Sina on the call to talk about that since she was driving it. It doesn't appear so but what's Watson's here but I don't know if you had a lot to do with it. Taylor had put himself down this reporting but I got. Oh, we don't feel on the call. Okay, Taylor do you want to discuss. Yeah, how do y'all, I am trying to see if I can bring up the actual poll results here. No, look here. Looks like we had pretty sharing or. Yeah, if you can share the results on that would be fantastic. You know, I'll lead to the results would also be useful. Sure. We had a thing at what is Watson on also. I see here. Okay, hey man. He may want to speak to how cumulative voting works in general there was a few issues on the, how the votes came in, but I will share them and then go through that. So that the voting I think we can will be okay as far as like what the results look like they're probably going to look a little bit funky for what may be expected. Wow. Taylor you're really building suspense here and I'm on the edge of my chair. Here we go. Don't worry. Tom is easy to put in the suspense. It's easy. I can, I can share my screen as well as that. You said it so that people can view it right now. I can't view it. Yeah. Thank you. You just said I'm the suspend signal and he's in the state of suspense. This is the problem with Colonel guys there. They're ultra responsive to signals. So some of that. Here's, here's the results just from the, the form that we created. And the funky thing here that you're going to see is some of the votes came through where they, the actual votes which it was supposed to be eight points total. And if you think of dot voting, you would take those points and put them on the time and date that you want. Potentially the original instructions didn't have enough on that. So we end up with some votes where eight was placed as yeses and zeros as nose. So some of the numbers look a little weird. But should be okay with the time because it's basically the preferred times. Everyone else it's okay. Thank you. We can do this. So it looks like this one's the thing. I think I'm one of the offenders in the way I voted. I had, I put multiple cuts. I looked at it as like ranked voting. Yeah. Correct. Apparently. So my totals might have been more than the total amount. Yeah, and I, I was actually trying to go in and see if I could like turn them all into proportional, which is what some of these are about. And so this was a proportion of the total. It just didn't work because some of the others instead of being ranked like that were literally like a proportion amount. But if I delete these, those aren't, they didn't actually help. I mean, it's almost feeling to me, I mean, we had an interesting suggestion for this proportional voting. Yeah, we should just drop back to doing a freaking doodle poll, because that's it works. And the real question is, is, is, can we maximize the ability of the community to attend the meeting. And the doodle poll is literally just a I can make it, I can't make it in the generic. Does that sound reasonable to folks. I think we end up with the same amount anyways, from what we were saying here. It's still the, it's, we ended up with proportion at plus the point so it seems to be okay. Watson, do you want to take a look and say he's, he's done a lot of the voting and calculations and could communicate how the, the dot voting would work with ranking. Your audio is a little quiet. Better. Yes. Okay, cool. Um, yeah, so with the cumulative voting. Basically, if you have a situation where you have a group, and you want to, you know, like what you were saying wait, I heard someone say wait the votes and I was saying cumulative voting. Basically, we almost had it, it's just that we needed to have some validation that just says hey, the maximum amount of points you see if you have eight points you have eight choices you have eight points, you have to distribute them. Put them all on one you can spread them across. But that way, the people who, you know, when you have a second choice everyone agrees on their second choice. It rises to the top, whereas if you just do yes no, you have situations where you have, you know, the majority loves one place but they're okay with the second, and the majority. I think maybe it will help me understand and I literally don't haven't thought it all the way through is what I can have is if a minority really really likes a particular day, the majority can't make it on that day. And then you have this smearing of points across other days by the majority where there are dates that more people could make. It's just that a minority really really like a particular day. You could wind up with a situation where we have a day that is, you know, not actually maximizing the ability community to attend. Right. And, and so the way it happens in real life is we actually it doesn't happen in a vacuum right we actually communicate. So you communicate before you put the, before you put the options out you communicate after they put the options out you're like, I like Friday I like Saturday. It's not like you're doing it in a, in a secretive way where no one Right. So community voting assumes that you will communicate and you're actually trying to find out, right. And so you can tell what you're talking about a coalition can be formed and dominate, which is like a minority but only if everyone, you know, actually doesn't act in a democratic fashion communicates on and trying to solve a problem because majority will still win. If you actually communicate. So, yeah, so I mean, it does look like the leading candidate is the current time I do know this is kind of a brutal time both for Israel and also for Europe because it's basically, you know, evening Friday night for Europe. It looks like the sort of second most favored time is on Tuesday seven to 8am. There are four people who couldn't make that versus six people who can't make this time. Right. So if you count the zeros, which is kind of the thing that I'm looking at here. There 12345678 zeros on this time. And on Tuesday seven to 8am there 12340s. So it does look like this time has this time does have, wait, I was kind of the wrong number of zeros I was kind of the wrong line. So Friday eight to 9am is one. Two zeros. Right. So we have two people today. So it does look like today actually also maximizes the number of people who could make it because I don't see any time that has fewer zeros. Right. And it minimizes the people that hate it. Also true. This is also true. Does anybody else have any thoughts or feelings or do you want to just continue with this time. I'm open to sort of continue to try and figure this out. Or we can just say, okay, we've done a lot of work in figuring this out. This doesn't appear to be the best time. What do folks think. You could revisit the issue in a couple of months or something, you know, after anger starts to accumulate if there is going to be any anger or feedback. That's also the suggestion. And membership could change over time too. So that's a good reason to revisit it in a couple of months. Yeah, that's exactly right. I was going to say that as well. You can kind of see where things evolve. Right. Good idea. I support that. It looks like the totals along the bottom pretty well. Say what Ed just said, so they're pretty, pretty accurate, even though some people did wrong. Well, and if Watson was really good about highlighting the zeros that hold me tremendously, I appreciate that. We could also, if when y'all are ready, whether that's for the next, maybe next month or a few weeks out, re-vote just with those three. That's also a possibility. So shall we sort of, does anyone have any objection to tabling it for the moment and, you know, stick it as something to pop up again in a few months and see where we stand? I think that's a good idea. Thank you so much. Thank you so much, guys, for the mechanics of the poll and presenting the data. It's not a trivial amount of work and it's very appreciated. You're welcome. I concur with everything Ed said. He put it way better than I was going to. But eventually, that is how I feel. It was an interesting exercise. We also learned a lot as well. Like next time we approach this, we'll take our learnings that we have now and apply them. Just make it clear on that it's accumulative and not ranked and then it would even be better. Or if we decide to be ranked, make sure it's clear that it's ranked and not accumulative. Somehow I missed the message. I'm probably not the only one. Okay, so action item Ed, did you ever get around to documenting the namespace? I did and let me actually put the link to that in. I did document that. I would like to do, I'm probably going to go back and improve the degree to which is documented what I essentially did was I documented how you figure out from inside a pod information you can send outside the pod that will allow you to know what the namespace of the pod was and there's a link to it there and I'll stick a link into I'll stick a link in here. So that it's in the meeting minutes as well, but the net net is you can actually find out you can always find out inside the pod in proc the I node of your network namespace. And if you are in a position to be mucking with network namespaces anyway, which the NSN has to be, then you'll have access to something like var run that NS where you can look for that I node and that gives you the name of the network namespace to work with and a file you can grab a hold of. So we can send to find information in the pod that we can send out of the pod that will allow us to figure out the network namespace. Well, and I posted the link to the week to the wiki as well so there's a lot of to do items if anyone wants to pick any to do item up and work on it it would be highly appreciated. Otherwise I'm going to be working down them as well. And that that can be seen on the bottom of the wiki getting namespace from inside a pod. And john is also added a how to install and run the network service manager on on GKE. So he's he's outlined each of the steps and what files you have to create in order to in order to kickstart it. So right now, my understanding is it should just actually mail that john talk about it. I'll try to find the unmute button. Yeah, it's not really fancy. It's just I ran it and there's a couple of I am things we had to get to change show how to set. Apart from that, it's really just taking a snapshot the current code and getting it to run just like runs today on minicube. So there's nothing that you know fancy so please try if you need to use GKE try it. And if you have any problems, let me know and I'll update documentation and try to help you. And if anybody wants to go try it on other cloud providers, additional wiki pages would be awesome. Yeah, and something that will be useful is as network service manager starts or never service mesh starts to change and starts to change. And if we have people who update these documents on a regular basis, that'll be very useful. Let's see. So review of recent development activity. So we've had a really busy time in the past in the past week so the first thing was we got a couple fixes in for for create CRD. We now have device plugin support. We had a device plug in some device plug in work but my understanding was it was incomplete. And so now we have a device plug in that. So from an architectural perspective, just to make sure everyone's on the same page. One of the things that we do is we have a set of Unix sockets that exist on the host and we use the device plugin API to expose a Unix socket to the to the network service manager client that that that exists with the CNF that you want to deploy. And so this particular Unix client is allocated using the device using the device plugin that is that is within Kubernetes. So that code landed a couple of days ago. And we also did a couple improvements to the CRD to have them use a single shared informer. So that should that should reduce memory footprint and reduce the complexity of the of shuffling of shuffling around different different informers at this particular time. Finally, we've been working on what's an informer Frederick. Oh, an informer is a Kubernetes construct. You can think of it as a it's a mixture of two things. I guess how to describe it. It's sort of like a listener that that emits events and Kubernetes and it also caches events for you listen. What's that a listener that sends events listens for events. It informs you it listens to the Kubernetes API and then informs you of changes. Okay. So, so these are part of the Kubernetes client client APIs and initially we were creating multiple informers turns out that we only need to create one and it's then everything still works and ideally should should work more more efficiently. And the last part that we've been working on and this is still active is we're working on. We had a version 1.0 or 0.1 of the network service of like getting a pod to the networks service mesh demon. And so now that we have the the Unix talk of landing where we can use it, we were revisiting the client connectivity API and iterating over it to try to work out what kind of messages can we can we send to like how do we request the connection how do we how do we expose a service and and interact with the network service manager and how do we set the labels for for a given connection to requesting and specify the type and so on. So, this is probably one of the more. I would argue this is one of the more important parts that we're going to be working on over over the next several over the next several weeks so if anyone wants to get involved with this conversation. And share share your experiences as to like based upon what you know of the domain like why this would or would not work that would be incredibly useful. So, feel free to join in on the on the conversations there. The best way to join in in these particular conversations would be in two areas one is to look at the and work on the pull request that's been set up. And the second one is to hop on to IRC onto the network service mesh channel and you read after you read it also discuss ideas and then we'll take those particular ideas and stick stick them as comments to the pull request. Yeah, one of the things that's probably worth noting is, this is something that's not going to set in concrete for a little while. So, you know, it's very much a how can we get shit working. So, while, while more feedback progressively as we go is important, don't feel like the train is leaving the station just now. That's a terrible feeling. Yeah, I completely agree with that as well like the, this is going to evolve as as we get more use cases involved. The time when it becomes set in concrete is, and it's going to be malleable concrete to a degree is going to be when we get to the to the 1.0.0 release, because our intention is to use semantic versioning. And so, hey, that's, that's what we want to be very careful with with changes and that's not to say that we can't change it at that point, but it's with the realization that if we do change it then people are going to people who are depending on this are going to have work to do in order to ensure that they migrate because of a backwards and compatible change. So, so before 1.0.0, like, if you see something and you feel like this is like the wrong direction or we're missing a use case or some important detail, like, bring it up, like, you know, even if we have even if we have a release date. I would rather push the release date back and get it right, rather than ship something that this is something big. So, cool. Awesome. And many thanks to Sergei for all the hard work he's been doing on a lot of this this week. Definitely appreciate it. Sure, it's fun. Can I can you so hear me. Yep, we can hear you. Cool. Sorry. Okay, it doesn't look like there's a critique that's on. So, yeah, I think them in IRC. And he and I spoke last week. So, I was hoping he might be able to join but what I suggest is we skip this part and if he if he wakes up in IRC and sees that we ping him he can join in and then we can come back to it. Does that sound good. It sounds good. So, getting getting started documentation and and and I added that based on our agenda bashing that we had earlier. Does anyone want to take any action items to help improve this. Yes. Okay, so what do you want me to write down for the action item. Well, I don't know whether I can get it all done in a week, but I should be should be able to make some progress by next week but I just want to start. I want to. I stopped working on on anything here for a few weeks and I want to start again and start from scratch and document every step I'm doing so that others. That would be massively helpful. Thank you. If you document, Tom, I'll try and use it so. Okay, and find my lies. I'll find out where I'm just. Find where we have differences in the things we find obvious. It's often the cases and assumptions that things are obvious are often the issues. You know, people say priority knowledge and so on. You know, I'll just go at it from my point of view and I'll probably and we'll see how it works out. And it's an opportunity to learn while I'm doing. And at the risk of biasing you if you need any help with anything, let me know. Thanks Frederick, I will. Okay, is there anyone else who would like to help on that that wants to take on any action items. Okay, if not, then let's move on to the next topic. We have the intro to the CNCF CNF project and NSM alignment. Taylor, I will hand the floor over to you. Awesome. So, let's just try to get some that ready. Kind of spread across two repositories right now. Share my screen. So, the actual CNF project repo itself is right here. I can drop that in. Where's the chat go when you are sharing. So we have two main repositories on this. And the first one doesn't have a lot of info. I'm going to give it because that's where we're moving to work. Some of the similar stuff with what y'all were talking about with the wikis and everything. This project is tied in with and let me do one more. This BCP use case, which is bring this up on the right screen. Also, as a question, so I think everyone should know what CNCF is, but it would be good to describe what CNF is and what your mission is as well. Absolutely. Okay. So, we are at Watson's on this team as well. So, we are part of the cross cloud CI team. And that's actually tied on to an action item for later as well. So, that's this project here. And we helped build out the dashboard for the CNCF. And we're helping now on this project for trying to convert or port or recreate, depending on how you want to look at it. The VNFs, so virtual network functions to work on Kubernetes and as containers. So, that's the end goal. And what we're looking at is these containers here, which that's on that. The link I gave to this wiki own app.org. So, looking at the different functions like the broadband network gateway, this VNF and this gateway here, all of those, including stuff like VDHCP and DNS, all of these pieces that tie together. This particular use case is of interest to folks like AT&T, Wall Way, Orange, Telcom. And this implementation that we see here in this diagram is the, all these network functions that are built and running on VMs and OpenStack. So, and this is actually a pretty old diagram. And the setup was, I think, originally a little over a year ago. And what we're coming in to do on this particular project, and there's not a lot of info on the front page yet. It's actually more of its own tickets that we're trying to build out. But we are doing a comparison between containers running those, the functionality and the VMs. A lot of the work the last few months that we've been working on is trying to get up and utilize what the own app group and Intel and all the different folks have been working on. I apologize. I think you said I explained who CNCF is as well. So that's Cloud Native Foundation. So the foundation is interested in trying to get any software working as Cloud Native and containerized and portable across the different clouds. So that's kind of been our focus with the CI stuff. This is a dashboard and focus on trying to get projects to actually work across the different clouds. And so our goals on the CNF project are to take these different VNS and make them portable as CNS containers and have Helm charts for installing on Kubernetes if y'all are familiar with that and make it real easy to do that. Potentially rebuild the actual use case to be that this was originally more of a demo. So trying to get it where we could chain those different network functions together or easily on top of Kubernetes. And so the big interest for us is going to come in when we get to building out the use case with the interest with NSM is building out the use case. So looking at how do we actually have routing work and all the other things that the network service mesh is trying to resolve for Kubernetes. So doing stuff like the DNS and authentication and building those out and making them talk is something that's solvable right now. It's going to be chaining these other pieces together to build out this use case. So right now we've this originally what we were focused on was understanding what all they had and most of the stuff again is kind of in the projects and issues will be building out the wiki and read me based on what we've been doing the last couple of months which is really digging into the demo code that was available. Again that's this tied in with this own app and a lot of it built on open stack and taking that apart and figuring out how all of that was working in a demo and then taking that and we're looking at building up the comparison between each of the different containers to their equivalent VMs for the network functions. And we're started working through this and we'll be having stuff like a vagrant file for the VMs to bring up the those VMs on KVM is what we're targeting right now and Docker files for bringing stuff up on Docker. This is kind of our first area for testing performance and the next set will be where we may need to pop into the there's no tickets here. I'm going to last time. So a little bit easier. So once we're once we're through building out each of the different ones like the V-Bang and all of these tests, we're planning on bringing up we'll need to bring up Kubernetes and look at how we're going to test. What are the minimal parts that we need potentially from the NSM project to get going. And then at some point we're going to be into this next section so actually comparing how things work on Kubernetes compared to open stack in the actual use case. That's when we go back here. So we're going to need to set up some type of configuration hoping that fingers crossed that we are by the time we're at a point to set up the use case. There will be enough parts of the network service mesh in place that we can fit these together or start fitting it together. And that's kind of the goal. I'll take in so if y'all have any questions we can kind of go from there. So I think this is really cool because I could easily see something like this being a good proof of concept for NSM to apply to. Absolutely. You know because you guys have the need to do the things that NSM does or is in the process of getting to do. So it could be very cool. Yeah and this could go down a couple of different ways. I'm thinking we're probably going to end up with a lot of contributions back to the own out project where they do management of all of these network pieces and potentially they would be. They've been working to port that all of that software onto Kubernetes and the recent Beijing release that they just had will run primarily on Kubernetes except for a couple of parts. Well once you start dealing with all of these other network functions they will need something like network service mesh. So I can see tying that in as one area to show off. Here's what as a I don't want to say proof of concept but somewhere where network service mesh could really help. And then I see potentially we're kind of in the early stages of this build out but potentially having a non on out maybe a clean room version of the this use case built out that would be a really good example what Ed was saying. And I think it was on the agenda the. The OSS seminar that's coming up bring that up really quick. So this is going to be talking all about that open source summit. This will actually be talking about a lot of these topics so cloud native functions on Kubernetes and and where this stuff is going so. So I would strongly encourage folks to go to that seminar at OSS it looks like it's going to be awesome and it would be great to have more NSM people in the room. Yeah and specifically it's the day before the conference on Tuesday so be aware of that if you're planning to to come to the work to the working group. Absolutely it's mentioning a lot of projects it doesn't I don't think NSM not seeing it here but we have a lot of the other related projects are listed on here so. Taylor could you please post a link to the own app document I just lost it the own app document you were showing. Yeah that one yes okay. Let me see if I can. I found the chat. If you can post the IRC the IRC is a little more persistent than the meeting. Yeah. The meeting chat is great for getting in front of the people on the meeting totally agree. If we could mirror that to the IRC channel that would be awesome. Yeah absolutely I'll log back on there and post some of these links related to the same enough including the. Cool sketch. Yeah, this is also be a good place to good just to come the wiki as well. Okay, cool. So I think the wiki should be editable by by everyone and so we'll try to keep it editable by everyone as long as possible. Hopefully we won't run into any random random idiots. The only concern I think if you do have to have a github account. Yeah, pretty fair and reasonable. You know the wiki can definitely accumulate things. Sounds good. I'll create a maybe a sub page about CNS and and where that could tie in. Yeah, that would be fantastic. Also, since we're talking about the wiki, I did want to sort of crowdsource one idea, which is if any of you guys have seen the Kubernetes story of Fippy. If you've not seen it do go look for PHIP UI Fippy and Kubernetes it's awesome. It's sort of the story explaining Kubernetes as a children's story. And I've been kind of mulling doing something similar for NSM but I need a character to in the character name for the protagonist so. You know if you guys have any interesting ideas please please surface them at some point. Ed with his red cape. I try to be a little bit less self self-indulgent than that only slightly. Okay, well down the list Hermes messenger of the gods. Okay, so see we have. We have eight eight minutes left. So do we Partique, do you think that's enough time to to discuss or should we just jump straight towards our action planning for the next week. I don't have much but I can take maybe like two three minutes just to give a very high level of what I have read so far and see how others are doing and get a feedback if that's the right approach. Okay. So I went through the studio documentation and through the Kubernetes so for the sidecar what they're doing is there is a new concept beta in 1.9 Kubernetes, and it's called mutating admission control webhooks. So the idea is when you when you submit a deployment of an app you get cube API server calls your API and you you're running a server inside the cluster and you get all the details about the admission and then you can mute it you can patch add a container add a volume or add any other that's how you can add us and the sidecar inside that pod. And that's what I have listed a link in the meeting minutes document about that also. So, if folks thinks that's the right approach we should take I can spend more time and I'm working on the document to to write the document in detail like how we can go about that. It certainly sounds potentially quite promising. You know, I don't think any of us actually understand it well enough to know one way or the other. But but it certainly sounds very interesting to me. So maybe a little more detail might be helpful. I've done some work with the webhooks and I mean in the newer version of Kubernetes it is the way to go if you want to inject anything in the port. I mean, automatically, not the injection. Okay, cool, cool. So would you be thinking that we could use that for injecting like in a container or something to to set up the connections to various or side or a sort of sidecar in the pod to talk to the NSM to set up and manage this stuff is that the thing you've been thinking critique. Yeah, exactly. Yeah, that sounds very promising to me. Yeah, how does it solve it? How does it send everyone else? I want to explore this approach a bit more. I guess it definitely sounds promising. The next section I don't know what I'll do is I'll try to create a document and what all what all components we need because whenever going through looks like API is the endpoint which is encrypted you need certificates which API server knows about so all that kind of stuff is involved here so I'll try and get that part sorted out. Thank you. Thank you all. I mean, particularly it'd be good to put a reading list on the wiki. So we go and catch up. Now that I see there's a wiki in place, I'll add it to the wiki. Give us all a chance to read and then figure out then we have discussion. Thanks for thanks for jumping in and taking a look at this. I think it sounds like everyone's pretty excited to see the results. So much appreciated. No worries thanks for thanks for coming in and discussing with a little bit of time. So, so we have four more minutes I want to make sure I got all the action items lined up properly so top of the action items line up for the CI working group if you haven't if you intend to go. We have a distributed action item to invent a character for Ed. Awesome. So there's a show called Ed Ed and Eddie maybe we can take a reference from there. Let's see we have. We have Tom looking at some, we're looking at adding documentation to help people who are entering and getting started. We have Taylor who's going to add documentation for CNCF and for CNF and the project that he's been working on. We have Prateek who is going to document the sidecar admission process. And so, is there anyone that I have or anything that I have missed. One of the items that we have not discussed that you want to add yourself to going to add one more as well. Oops, sorry. Going to add that if people who want to get involved with the pod to NSM API. I'm sure for people who are looking at this, you know, feel free to feel free to get involved if you have the, if you have the time at this particular point as well. And, okay, if we don't have anything else are then let's go ahead and conclude and we'll yield back two minutes of time. So thank you everyone for attending. Thanks. Thank you. Bye bye everybody. Thanks. Hey, does there anything we have to do in order to get the recording back or does do it automatically. Sorry, you're on mute. The recording gets made automatically and then occasionally Prem and I get an email from the CNCF person because Prem's the one who made the arrangements and I'm the one who made the intro. If you want, I can loop you into that thread and we can figure out a more sustainable way of approaching the problem. Wait, there's a YouTube channel they're putting on and there's a link at the top of the meeting thing to the YouTube channel. So, yep, yep. Anyway, cool. I got to run to my next call. Talk to you later. Cool. Talk to you everybody.