 Okay, well, so from last week, most of the doc items were about the new release and versus previously, a lot of it was focused on the glossary. And I think there's quite a few folks that aren't available today, Frederick may be joining here in a few minutes can give an update, but Nikolai and several other people that had action items are available. We can go ahead though. Does Jeff, Joel, anybody else have any specific topics I'd like to go over? I'll just try to work through what we had. So the quick start guide, that's related to Nikolai. I don't think there's anything updated that I know of on the release notes. We're looking at what items would be available for the new release. And I think Fred, that's another item between Frederick and Nikolai. Let's see. We have here landing page that actually doesn't have anybody. So we may be looking for assistance on that. Videos and persona. Oh, there's Frederick. Hey, Fred, you know, it's pretty light today. So as far as like folks who could speak to action items, Nikolai is out. I don't know what's been done there. But we don't have anybody that's picked up anything specifically on the quick start guide and the different pieces other than Nikolai on STK. And he's not here. It almost, it kind of feels like we should have canceled today with so many people out. But do you have anything you want to specific to speak to? The release notes, I think we're action items. Yeah, so the release notes are something I'm working on. I don't have anything to show for just yet. I will have something for next week on the release notes. Especially since we have, you know, we're coming up to the end of the cycle. So in terms of getting started or rather quick start documents. So Nikolai and I have been working on our presentation for KubeCon. And one of the things that's occurred to me is that we're probably right now, I think we're only going to focus on like the generic quick start on like, how do you get something running? But it also occurred to me that having some form of a quick start, if you're a CNF developer, trying to write something on Kubernetes would also be useful as well. And so the documentation that we come up with or rather the presentation we come up with on that after KubeCon, we can use to seed that particular document as well. But other than that, I don't have a Nikolai status. So I don't know how things are on the generic quick start at this point. Well, you can put that in there as far as like idea is what it sounds like nothing started and maybe past KubeCon for CNF developer. Sounds good as another additional persona basically. Yeah, and that's actually how I'm trying to drive into this scenario is like similar to the Sarah use case picks to pick a narrative of a person who wants to create a CNF on that that runs within Kubernetes. And then the challenges that the person runs to with privileges with with a lack of of APIs and so on. And then gets introduced to Ariadneka then makes it easier to cope with. Sounds good. Having a story is helpful. Let's see. The alternative messaging for what is in some and who is it for seems related to this. Do you have any idea if that's any progress on that, both for the repo as well as the network service mesh website. I don't have any insight on to that at the moment. Pull it up so that we don't lose it on the videos per persona. There's going to be two parts one kind of a write up. That's the script be related to what we're talking about. This would lead to those videos sketch. Sketch not have videos and stuff that you've been doing Watson. Do you have any update on this. Probably not going to be able to start on that until next week. Be nice to. I think Josh is on the line and be nice if we went through and installed. And so I'm on the packet and you get a kind of feel what documentation is currently there and then trying to make it more concise for video or write a script for it. I don't know if you'd like some. Either feedback or help from anyone else. I don't know if like Frederick if you'd be available for. Speeding that up. Initial setup and walk through. With the current code base. Or are you wanting to go through it yourself and see how it is. I know Josh wanted to help out. I had what would be minimum requirements for a system if we're going to say spin up the claim system on packet for doing an install. And trying to. Come at it as from a new user perspective so. How do you use an SM. The first time. And I guess another thing we ran into was there's building from the. Containers the pre-built containers and then there's actually building. And I sound. From scratch and we went down the. Trying to build it from scratch and got a bit stuck there. So I guess there's two. Probably need to get it and probably be easier or better to do the operator persona first and build from containers and use whatever CNF is out there. First and then we can hassle people for. Getting an environment set up for actually dev. Environment. Yeah, so I think. And my preference for a quick start is if the helm charts already working to to go with that because that by far would be the easiest approach. So in terms of packet, I mean it's primarily. Getting a Kubernetes instance set up and that's to me that's actually the harder part is how do you get Kubernetes spun up. And then the second part is. How do you. How do you get. Network service mesh install onto onto that that cluster. And that would be the ideally the helm charts. And then from there the. We can then focus on how do you get the individual network services deployed. And ideally those should all be home charts as well. So we need to see exactly where we are. If we have enough implemented where we can do that. Okay, now then that would be. I guess, like we were saying the operator. Persona viewpoint just using helm. And it's installed that way. But as far as a developer. You know, having go installed and how your development environment is. For creating a CNF. That's another. I don't know if that works the same way as you're saying I was assuming not. Or there was some medicinal steps. Yeah, so it's creating a CNF. So. Ideally. My hope is that we don't have to get them to. To do a full install. But I think we do at the moment. So. But we. If you look at the. The examples repository. Those should should. I guess we would say Merley. Use that work service mesh. Rather than. Rather than require like to get people to be. Like fully installed and. And run the big files and that kind of stuff. So. Yeah. So yeah, it's all we saw the repo. There's two sets of instructions like the helm charts and then there's actually building it. So we'll, I guess we'll go down the helm first and do the operator persona first and then. The CNF developer environment would be pretty. So. A little bit of a broad. It shouldn't be specific to anything on. In a sum. Other than. The. In a sum agent or. Client that you may build. Add in like, if you're using the SDK, or if you're using the little agent. The rest of the environment would be pretty generic. I guess if you said what is the most minimal. And then you're using the SDK. I would probably say focus on. Using the SDK. Inside of a container. And that sounds like it would be better to do. Later. After doing all the other parts operator persona. And then in my mind, there's the NSM developer. Yeah, that's what I was expecting that. Yeah. So I was confused in those two. You're right. But CNF developer is, I think, a good idea. And that'll be. Go across. Both the. Network service mesh project, as well as the same test, but initiative. So we do need. To test using the NSM SDK so that we can start. Writing clients. And end points that can talk to NSM. But that sounds like the more advanced of the. Yeah. Three. Yeah. Well. Yeah. The more advanced seems to me that NSM, if that's what you're saying, the NSM developers. Probably should be done last, even though. If we want contributions, it should be. Probably done. First. So. So what I'm hearing is that there's, there's. Three personas that in the scenario that we're going to. They were going to look at. There's a couple more personas that we haven't. We haven't targeted just yet, but we'll eventually need to target. Which is going to be. Like, if you're a. If you're a. Jeffrey isn't going to go after me over this. Or maybe he will, if he listens in. But like the data plane provider. Like, how do you be a data provider? Or how do you. Or what if you're the Kubernetes operator who wants to deploy, but you're not. You're not the client. You're not the CNF developer. And so there's. And so there's a couple other personas which. We, we can also eventually write about, but I don't think we should hit those at this time. So I think we focus on the CNF developer. Sorry, we focus on the client. We focus on the CNF developer. I think we'll get the most bang for a buck there. And then for new people who want to develop on an assembly. Of course we want to make that easier, but. It's, it's not a high priority in terms of like. Onboarding. The larger community. Okay. What are the, from an operator persona perspective. If there's multiple operators, what would be the. Top. The top one and maybe thinking. If you only got one done by cube con, then what would the operator persona be? Someone that's taking using helm to deploy. Network service mesh. Yeah, I think that'd be the, the easiest one using help to. To deploy network service mesh. And to deploy some network service and planes. Like maybe. Similar service. The users can then begin. They're provided as services. For their. What do you think would be most useful then for. Cube con. Attendees. Anything. Go ahead. Just based on the time, I think. We, we definitely have something for the, for the clients. I think to be honest, the client one would be. Well, by maybe the. The CNF developer. Because the CNF developer, even though it's a little bit of small crowd at the moment. I think. Over the next six months. That's going to. That's going to become a more. More. If we have preparation for that. It's this particular. I'm not suggesting we will get to it. But if we were to have it, then. As a stretch goal. That means that any, any material that gets done here. In terms of lateral or, or. Videos or so on. I think would. Would be. Very helpful down the road. And. Watson, do you think you have enough to get started with Josh? Yeah. I mean, we. We just asked us. Now that we're folks on operators. Yeah. We can. Get to a point to where. We can ask for help. I'm going to swap these around. Where it has the CNF developer next based on what you're saying. Fred. Oh, if we have. Network service mesh going. Ideally. From the operator perspective. So it's been deployed. Maybe there's some pre built. Test CNFs or whatever a VPN endpoint or doing something. So going through that. Watson can work on. Making sure that works with Josh. Getting it scripted out. And then. We'll be able to have a video tied into that. After that's done. We can look at from a CNF developer standpoint. Using the SDK to bring it. Build a client endpoint. And. At that point it'll build on the operator personas. So you'd say we have network service mesh going. Now we've built a new CNF. And here's how you use SDK. We're going to deploy it. To the. Network service mesh enabled. Kubernetes cluster. And see how that would work. So it could build on the last one. And then the final one. At least based on. What we have right now that I've written out is. And that in a sim developer. So someone that actually is trying to modify. In a sim directly. And what would they do. What do they need to get set up in their environment. Does that sound good to y'all as far as like. The direction. To build from. Basic clients. Like here's how you connect to a network service before we jump into. So would that be a prebuilt. Client that could be. Spun up on a cluster that already has. In a sim. Enabled from the first one. Your audio is cutting out. Fred. Your audio. Can you say that again. I'm not hearing anything now. If anybody's saying anything. Fred was reconnecting his audio. Fred you want to try again. See if the audio works. Okay. He's dropped completely. Maybe he'll come back. Oh, there he is. Video and audio again. Are you able to hear me now. I can hear you. So you were talking about the client connecting to NSM, which is between the operator. And a CNF developer. So how do you connect a client to NSM. So I think we just show the most basic version of it. So I'm not worried about shared memory or anything like that at the beginning, which is, which is, should be quite easy. You just annotate the pod spec. When you start up with the network service mesh. Labels. And then the mutating access controller will do the rest and we'll inject the interface in. So that should be a, that should be a very simple one. So just, you know, show the annotation. Hit, um, apply, apply it. See the pod come up in a network service. Okay. Sounds good. So what's, do you have any questions? Yeah. It's going to be cutting it close. So. Yeah. Yeah. I think that's good. You eventually. Shared memory one, because I think there'll be a lot of interest there. But I think just even just showing off just the, the basic. Like Sarah style. How do you connect her pod to the VPN, which is just the annotation. And so I think it's very, very simple to get started. Okay. Start with the operator persona. Just getting. The NSM components deployed with him. And making sure that. That can be repeated and. Have a script for that. And I think that's a good starting point. That'll make a small video. So here's how to get an SM. Running on a Kubernetes cluster. And that's before you. Have anything actually talking to it. And that'll be the follow up video. Okay. I think other items like the glossary. Was deferred previously because folks weren't available. They're still not available. So. We can defer that one. And that's really it as far as. The items on the agenda. Most of them are deferred because folks are out. But I think we got through everything with the people that are here. Does anyone have anything else? Thanks everyone. We'll see you next week. Yeah. Great. Thank you very much. Cheers.