 Might be a very short working group meeting and just sort of get a recap in and a status on some of the stuff from yesterday. So, I'll figure out and I'll hopefully get everything edited and up tomorrow from yesterday's thing. I just really wanted to say a big thank you to. To everybody for for all the effort that got put into doing those demos scrambling for resources to be able to deploy things. And it was pretty amazing. So, I really, really, really appreciate it. And we did. I don't know if you are watching coupon, but on stage this morning. Much to my surprise, I did not know that was going to happen. Okay, you got a big shout out in one of the keynotes that red hat did. Yeah, that's nice. Yeah, so red hat had a sponsors keynote. And we decided to use it for saying happy birthday to OCI. Irvashi Mohani and Sally O'Malley did the presentation. And in it, they mentioned okay D a couple of times. So I, I tweeted that and that was, that was really very nice to see because we don't, we don't have a lot of brand recognition out there. Shall we say we're kind of overshadowed by our big brother open shift. But that's, that's okay. Because we get a lot of benefit from that too. So, yeah, so that was really nice. So I don't know is everybody on this call also following along on coupon. I, I hadn't, but I probably will because why not. All right. Well, in the chat, I put the, the Google doc again. So if you're attending, if you could sign into that. Yeah, but to see how much they're going to make me pay to do it, but I'm, I'll probably show up because why not. Well, the thing, I think the cheaters way just the back door and I'm recording this is if you are a member of the cloud native foundation Slack. If you're there, if you go into the Slack channels, you'll see number 1, number 2, number 3 and all of these other slack channels that are set up specifically for coupon. And to be quite honest, I think the more interesting thing today, there's chat through the intrado platform hosted thing. And really hard to figure out and disappears after the event. And then there's lack that the cloud native foundation has set up for all the coupon different tracks. And so I'm hanging out in Slack. I have 1 window open for the booth because I'm on booth duty. But I would say that the slack is really where the networking is going on. Sure. And you can always watch stuff after the fact that there are live after each talk in intrado, there is a chat room for this in Slack for those speakers. Well, then pretty much everything is pre recorded for coupon. There's very little live. Oh good. Well, then I'm just going to sign up for yet another slack workspace, I guess. Because that's, that's probably fine. I'm sure. All right. So today I'm going to share my screen. Hey Christian. Hi. I think we're all a little burnt out. I'm a little. Yesterday was. By the end of the day, I actually literally had almost lost my voice because I was. Maybe not talking as much as some of the presenters, but it was I first used of my voice after vacation. I wanted to say again on record. Thank you to Christian and Charo and every 1 of the working group members who presented it was, I know a big effort to get the resources to do that Charo. I know we just hired you and we put you on the red hot, red hat hot seat a number of times, but you came shining through. You know, Neil, you and dusty. I so appreciated having the fedora representation on that session that was you couldn't do better than that. Well, thanks. You really can't. And I need to, and I know the open stackers aren't probably here today, but it was wonderful to close on the open stack 1 and have that private cloud full open source stack as the closer. So, I'm going to start making a bigger deal and try and get some of the open stackers to come more often to these things. But that was for me that was really good because the, yeah, bringing that community into was very, very nice. As far as viewership, I think over the arc of the day between what I could see with interactions with people, we had about 100 to 125 unique people who actually were engaged in the day. Who like asked a question stayed online for more than 10 minutes or whatever it was the actual viewership, which is different than engaged people. They were from Facebook alone. There were 700 different unique viewers. And in Twitch, there were 600, not 600, 465, what did I say, 462 viewers. So that's people coming in at different times, whether it was from the tweets looking for a few minutes. And I don't have the YouTube live stuff because YouTube, unbelievably because with Google compute, you think they'd be faster. But their analytics page only shows the number of people who engaged in 146 people engaged. But it's kind of wonky and the viewer number is usually bigger on YouTube than either the other two platforms, but we won't know for a few days. So the other aspect of this is it's, it was a very long day. And which you saw in blue jeans how I paused at different points to grab chunks so that I could download the videos because the videos, if they're longer than two hours, it's really hard on anybody's computer to edit the videos. So it's going to take me a little bit of time to edit all those videos. I thought I could turn them around last night, but it didn't happen. So and coupon is happening today and tomorrow. So I'm going to try and get all of the videos done and out the door, at least on the playlist by the end of day tomorrow. And that'll be pushing it, but that's, that's my goal. I also, I'm going to get dental work done tomorrow afternoon. So, you know, you'll see how that all works out. So I am, I can't say enough that those kinds of events are huge for us building the brand of okay D. I can't, whether I said this before, I hit the record button before we also got a shout out this morning on the keynote stage at coupon. The red hat sponsored speech, which we never really do to talk about ourselves or red hat products. We used it this time to say happy birthday to OCI. Open container initiative. And in that, for Vashi Mohani and Sally O'Malley did two great mentions of okay D as users of OCI and, you know, and so we got some brand awareness from that, hopefully. So if you look on my Python DJ Twitter feed, you'll see that I took a screen cap because I was so surprised and did that. So that's really for us now. There's two sides of the coins is continuing to do all the work that we're doing. Building on getting the operators there and everything else and keeping the buildings cadence and incorporating people's feedback. So that's the work that we normally do. And also starting to engage with the public in terms of people who are using okay D. And so one of the folks who was on the call, most of the day yesterday was a gentleman from Red Pill. And I think Neil and I were talking about this a little bit in the chat on Red Pill is is migrating from 311. Okay D to four. So pep and is a great news case for okay in production. So I'm going to start looking for those people and try and get them to do little case studies or little snippets that we can publish and because I don't, there is no gatekeeping okay D. We really don't know who's using it. You know, for good or ill. Yeah, for good or ill. And we do know that it gets downloaded quite a bit. I don't have the numbers or the stats or anything, but there's just basically no gatekeeping. So it's engaging and doing things like yesterday help us get these people out of the closet, get them to give us feedback and enable them to do things. You know, enable us to know what they're doing with okay D and get that feedback into open shift into all the other things as well. So that's, you know, that's sort of my quick and dirty update on what's going on or what went on yesterday. I will as soon as I get the videos all up done. I'm going to do a recap blog post. And if you had slides that you did with your presentation. Share them with me at their Google slides and I'll include them in the recap blog post. And I'm theoretically I'm supposed to have that done by the end of day Wednesday but I'm getting a crown on my tooth and that's just not going to happen tomorrow. So I probably won't be talking on Thursday too much after they grind down my tooth. So anyways, that's my spiel. This is my gratitude. This is one of the things I'm grateful for you guys for doing all this work. So thank you. And so I'm wondering if you have any update Christian on okay D4 to share with us today or where we're going. Yeah, just a short one maybe. So for 4.6 we're still experiencing some issues with OVN. It's on master so the same with OCP. Yeah, working on that to get preview builds for open shift or okay D4.6 as soon as possible. And yeah, Vadim has his anniversary today so he can't be here. I think that's a good excuse and he's also working on preparing a new version of the dollar. Yeah, that's kind of the quick updates from me. I haven't had time to to write up the enhancement for the operators to get them released on okay D more, but that's going to be happening before next meeting. There was yesterday there was a mention about the Fedora containers. Yeah, I think Clement Timor is back from PTO. I'll reach out to him as well and set that up. I believe that he wants to set up some kind of dedicated workshop to like kickstart the whole thing. And so we should figure that out and get a date set up and maybe take advantage of the fact that Fedora now has this virtual platform thing. So we can all like just jump in and start figuring that stuff out. Yeah, so I think you're referring to hop into that we used for Nest and I have actually I have access to it as well. I paid for it. It's a nice system. I was generally pleased with it. Yeah, we pay we or I didn't pay for it, but I paid for half the contract for it. So Ospo, our open source group paid for one half and I paid the other half. So if we want to host a joint meeting or something like that, we should try and do that. So let's maybe we could get Clement to come do one of these and we can just discuss how to move it forward. Yeah, or if Clement and Christian want to chat about it and just let me know. Yeah, maybe maybe it's even going to happen before our next meeting, but I'll definitely invite him to come here as well. Yeah, we should do that soon. So I hope that can happen next week probably I haven't I was I thought it was happening this week, but there was no updates on the issue. So what I would suggest is that maybe we do something like a joint meeting, you know, KD working group in the container working group and maybe use the next two weeks from now time to do something and then just give him a half an hour to talk about what they what they're how they want to kickstart it or kickstart it then and do something. So I think he's really trying to set up a two hour workshop that kind of does work walk through and then also like a hacking session to get things started, because I don't think there's too many active members of the container stick right now. Let's come on we set that up. I joined in from the beginning and I'm not sure Neil you were probably there as well. I've been there for a while when it was alive and then when it died. Yeah, can you put in the chat. Can you put the link to their their landing page in fedora land for me and we can add it added in here. Yeah, I mean, sometimes when six die. There's a reason for it because there's not enough there there. Yeah, the main reason that the container stick died off was the the open shift origin community that essentially supported it in the beginning. Stop caring and open shift stop being buildable and runnable on fedora and a lot of the infrastructure that was being built around it was actually developed by the open shift team and those all brought it away. And so it got to a point where nothing worked and there was nobody there to help because nobody cared. And so naturally the stick just fell apart. And I watched that happen to so I just kind of, you know, and that's why I'm so thrilled about the collaboration and how it's worked with the fedora coro s group and I'd like to like to make sure that continues to happen here so to see if I have your chat here. There's actually the issue. I just pasted it in the chat about the next meeting and somebody posted a when it's good, which I think is probably like a doodle to find the to find a good time for everybody so you could probably just enter. Yeah, whenever you can in there and then we'll hopefully find a good time for everybody. Yeah. Okay, good. That's a good one. And then we'll just grab all I'll grab all of that. Put it in the notes here. You're getting to listen to me all the way back. So that's, I think that's our next thing prior figuring out the, the operator roadmap is probably should be the major topic for the next. Okay, do you work in group meeting, if you're willing to take that on and get that issue listed. Good review that next time. What's that for me? Yeah, that was for your question. Yeah. I will try to write up the enhancement, but I am pretty booked for the next two weeks already. So I'm not sure how much time I can actually do and dive into the actual operators there. I will try to set up or to write up the enhancement though. So we can maybe use that as a starting point. Yeah, we can split the work if Charo can also help out maybe I would, I would like to, I would like to have a situation where not every work is only on one pair of shoulders. Because you don't, we don't want to wait. Yeah, always forward, always forward. Don't wait for anything like a train. Yeah, I think what my goal is, is if we can get the enhancement request put in and the ones that have other communities around them, that we work with those communities as well. So maybe the service mesh folks or whatever it is, but I think what we need is that starting point and that list. Yeah, we can use the next time to go through those and see where we need to reach out to people because the one thing that I'm a little concerned about is because their operators come and go and we are going to get more and more of them. Is that if we're holding the bag. Excuse me for maintaining the community versions for okay D and we don't have a connection to that. We're going to be in trouble. Yep. I mean, it'll be a repeat of before is which was we don't want that. So essentially what at least for the enhancement proposal what I want to make sure that all the at least the red hat. Made operators that all of them get released or okay D by their teams so we as a worker group don't have that additional work because we won't be able to do it. We won't be able to go into every operator and fix it up and then also maintain that for all releases. That's the thing the teams have to do themselves. It's essentially like packaging. You have to they have to release all that platform right and they have to do by themselves. One thing that I think would be and one thing that would be nice to see would be on the fedora side like giving people the tools and tutorials and things like that for being able to build operators because like I want to build an operator and I have literally no idea how to do it and all the documentation I read makes me more and more confused on how to do it and it's just I feel lost in the sea of. Buzz speak and confusion and technical confusion and that's not helpful. And in order to help better support having a larger community of operators, we should make sure that that is something that people can feel self sufficient in learning how to do this. Yeah, well, and the other thing is I can reach out to the operate. I also do community work for the operator framework folks. Once we have a there there, you know, we know what that hackfest is, we can get people like Michael Revnick, the Josh Woods J dobes who wrote the book on operators to come and participate in that. And so it's not on the okay D working group. Those guys are all three of them are awesome resources. And I think better teachers might Matt Dorn is another one that I've had come and teach at the Commons, how to build an operator and all they have to do is flex a little muscle to get it to be how to build an operator for okay D. Exactly. I think we should really provide that documentation and together with fedora make make that a clear path, but we have to draw the line somewhere between the okay D working group and the operator have a special interest group. For example, those would be the ones you may be wanting to approach for getting operators onto the platform. Well, okay D the working group. We're really just working on the core operators which are part of open shift. So anything else is like a feature we will not support from our side, because it's just not our realm here. Obviously, we want people to use that but yeah we're really focused on the core. So from my perspective, the way I think that that should evolve towards this. There should be a corresponding fedora SIG or team or whatever that is actually focused on building up fedora as a platform for making operators and supporting applications and stuff like that because the container SIG will help make it possible for people to have the the the ingredients they need to run applications on a fedora platform, but having the, the, the, the tooling to produce things to run those applications in in open shift or okay D or wherever or Kubernetes, whatever you want to call it. We don't have a specific group for doing that and the operator framework if it's going to build a community if you want to like, seed a community development and interest in this particular pattern of running services and infrastructure on on Kubernetes platforms. That's probably a place to start and so if there is going to be some kind of community there, maybe a SIG that's connected to fedora to do that would help make it so that it's a lot more accessible. But what is so special about running operators on fedora we are, we are using the operator framework since two, two years now. Nothing, there's nothing special. I think, I think what I would like to take a step back here for a second is I just think it's education and documentation. Okay, I don't. I'm not positive you need a fedora operator SIG. The main cause let me just finish. Okay. Red Hat has donated the operator framework, the SDK and the OLM side of things is all part of the CNCF and is an incubated project. So there will be SIGs over there for fedora people to join and they can create a subset there if they need to rather than a fedora operator thing. And I know that's not normal mode, but that would be to me the natural place to make requests for more documentation and to donate that and to build awareness for fedora in the Kubernetes world would be a better way for doing community development and doing some collaboration in that space rather than doing something separately that might die on its own if it doesn't have care and feeding from the operator framework community. So here's my flip side of this leave in the fedora in fedora there are people who develop applications and services for running to support the fedora community. Right now, all of those things are packaged up and installed on different VMs. The thing is, they want those to move to being things that run on top of open shift for good or bad. There are no patterns. There's no procedures. There's no practices. There's nothing for how to do that. If you want people to be able to do that, you need it's not just that there has to be a community upstream. There's always a community upstream for all the crap. I honestly doesn't matter. The problem is that you also need you need communities where people are actually doing work who are actually able to take advantage of those technologies. That's the reason why Linux distributions, while they like open Susan Fedora, they both use RPM. They both have their own packaging guidelines. They all do their own packaging stuff. But there's also the RPM upstream community where things that do make sense to put together there happen there. From my perspective, I see operators in the same manner. It's essentially the foundational aspect for delivering applications and services on a Kubernetes, for lack of a better phrase, operating system platform. Different communities are going to have different patterns, different styles, different guidelines, different tools. When I talk about with the container SIG and having people be able to make operators using those, the idea is that you take Fedora content and you build upon it and be able to make operators and stuff. And they would be pushed into Fedora registry that could even be pushed out to operator hub. That probably is a good thing to do. And there should be a liaison between the Fedora side and the upstream part. I'm not disagreeing with that part, but the problem is that without a way to distribute that community load, you have two potential problems. The first is there will be so many people in one spot that there is basically no way to give anybody any attention, which is what happens with Kubernetes right now. And that's why Kubernetes communities tend to splinter out and spread out and things like that. Or you start specializing in splitting and subgrouping and things like that. And that's the natural pattern that tends to happen already today. So you wind up having, you have an operator, you have a release SIG, which then has a sub SIG for XYZ thing. And those people just, it kind of fans out over time. And where that fans out doesn't matter if it's on CNCF side or the distro side or some weather else altogether. What I'm saying is that because we have all this, we have this nucleus of people that exist in the Fedora community to do these sorts of things. We should have them have the opportunity to be able to make these sorts of things. And with Fedora's upstream first ethos also help bring those and spread that back into the upstream project. So I'm not saying that you shouldn't have an upstream operator community because that would be stupid not to have one. But we also need something to support a diverse set of applications and such. Because I firmly think that what we're going to wind up having is we're going to have so many operators from so many communities with different opinions and different structures and things like that. That it's just not going, it's not going to scale if they're all in one place. And so we need to make sure that the community is structured so that it scales out past that, especially if you want it to be successful. I agree and I have it's kind of like software packaging for Linux distros. And we'll have to make sure that Fedora packages its own operators because we just can't consume or we don't want to consume operators that aren't built with our guidelines elsewhere. They may work, but they're not, you know, not specifically made for the environment. Which is the reason why I want to get the Rata teams who specifically also release for Fedora CoroS based operators. And then all the other operators teams that we don't really have, you know, influence on here will have to convince because they'll have to. I think it's easiest if it comes from the upstream directly if the operator team that creates an operator that they have a few release artifacts they want to push out every time and Fedora CoroS specifically for OKD to be one of those. So that is really the goal. I mean, if that really works out, we wouldn't need the operator sync in Fedora because there wouldn't be nothing to do. All the upstreams would release for CoroS. But I don't, yeah, there is a little bit of a middle ground. Not all the operators will do that all the time and there will have to be volunteers to pick up that work. And that won't be, yeah, exactly. Yeah, so I'm not anti creating anything here. I just think there should be some liaison, as you mentioned, you know, to the operator DNCF SIGs that are just now being set up there. Yeah, I think we should get the container SIG started again first then send the liaison from them to the operator, maybe send a liaison from us there as well. And then see how we can grow that operators in Fedora environment. I think it's Clement's idea of doing the hackathon workshop. And, you know, Craig put in the link to the book that Josh and Jay wrote. I think we can get them to come and, you know, help teach the class and give away the book and talk about, you know, how to get involved in all of these other places. But also create some educational materials that are Fedora specific that address, you know, things that are Fedora CoroS, things that are OKD. And as a starting point, at the very least. I still don't understand why, what is Fedora specific about operators, sorry. Nothing. The point is that Fedora makes infrastructure applications, and there should be a home for those people to come up with a pattern of how to release them. And you release operators as container images, right? So we want them to be Fedora based container images. And those will be running Superfine on Fedora CoroS. The problem with having containers like Fedora containers is they won't necessarily run on older kernels because they assume the Fedora kernel to be present. So only from that version up, it's really supported. And, you know, we wouldn't want to run container images on rail seven. Oh, jeez. Don't even go there. Like I've done that before. You get some very weird bugs when you do that. And on the other hand, we don't want to run, I don't know, Debian or any other container images on Fedora CoroS if we don't really have to. Because we have our own container system that is just out for running with the Fedora kernel with, you know, all the environment in place that the container assumes is there beneath it. Which is why we really want... UBI is a special case because it kind of just works on Fedora as well. But, yeah, and it... That's kind of the rel8 UBI universal-based image. So that works fine and is tested. But other than that, it should really be just Fedora container images running the operators or UBI. It could be both. But for Okini, it could be both. But you really want a container image that assumes you have a newer kernel there. And really the core of it is that because we're starting to have an open shift and there's this push from Red Hat and from other people that we should be running our infrastructure applications in open shift, whether it's a good idea or not is beside the point. That's sort of the thing that's starting to happen. We need to start having practices, procedures, guidelines and policies about how these things are made and released. Because without that, it's going to be insane. That's pretty much what it's going to be. And I don't want to make our admin's lives even worse than it already is right now. They're already having an unpleasant time trying to bring the community open shift back online. I don't want to think about how much worse it would be if they also had to try to figure out how to bring all the applications on top of it. And they all worked in inconsistent, weird ways that are not necessarily good patterns for handling those concerns. Because this is all new stuff. This is all new to everybody. And so there are very few people who understand what the good practices are and how this should work and how this is optimized for this case and that case and whatnot. And every application is different. And that's why it helps to be able to have that sort of thing, both upstream in the CNCF side, as well as handle Fedora specific things in the Fedora level for Fedora application. Yeah. So I think, like I put a link into the most recent operator intro workshop that Matt Dorn and Michael Revneck, they've been doing these workshops for all different flavors. Whether it's internally, externally, at different things, asking them and Jay Dobies. And we have four great people who basically are just spending their time now teaching people how to do this. And we definitely will work with Clomet to get them to help with the hackathon and just record their content and have it be Fedora specific or aimed at a Fedora audience. Probably is a better way of putting it. And then, you know, and then we can, and then, you know, spinning up the Fedora operator one, what we did for the operator while we were incubating the operator framework was we hosted and we have been doing this for the besides you guys work with them on a regular basis and then incubating, hand holding all of the different everybody from Cystig and Falco to a bazillion people writing operators and getting them to put them in operator hub.io in in the operator hub that's embedded in OpenShift. And we had to do a whole lot of hand holding and that's been going on for the past two years. So these guys now have it down to a science. How to teach it and, you know, and they can flip over to whatever the specific platform is or operating system or ecosystem that they're working in on a dime that you know so it's it's not like we don't have people to do this we just need the connections and a date and a place to do it. So I think you're on the right path Christian reaching out with Clement and connecting there. So for the ones that are Fedora specific Fedora community people want to have to run on OKD, we can we can we can manage that that's a that's a knowable, solvable problem. Maybe it's not not a great idea to add fragmentation there on the Fedora side by creating yet another stick, maybe the container stick can also be the because it's the same realm anyways. Yeah, we just need a place in the Fedora land where where this documentation and you know this knowledge building and sharing. So that for that that side of it. So when you're talking with Clement mentioned Matt and Michael and Jay and and Josh and let's connect all those dots there and I can help with intros or whatever. The other piece of it is supporting your request to the Red Hat engineers team to make sure that they do that and so we'll have to. There'll be some internal stuff that I'll have to help negotiate, I hope, and I don't feel like it's going to be that hard of an ask because there's a lot of automation involved. So it might be just that so there's this sort of 2 sides to this coin and and what you're going through with Fedora. We have gone through with everyone who's in the certified operator program at Red Hat. Everyone who's in the community side of things that are doing upstream project. Yeah, these guys got it so it's I know we can solve this so and and I want to solve it in a healthy good connected way with Fedora that grows both sides of the fence and maybe. Yeah, and for for OKD specifically we don't always need Fedora operators. So as I mentioned before the UBI ones are expected to work. So for most dreaded operators they won't even need to change big things in their operators they just need to make sure they. They respect the limits of the boundaries that Fedora CoroS sets them and I think the biggest one is that we don't have Python on the host in Fedora CoroS we do have in rail CoroS so many operators still assume that and won't therefore work on Fedora CoroS. So if we make them, I think we just had the bird, which one was it? Cube bird operator fixed for that and that's kind of the thing I want to see here I don't want to add X to work for them to release really a second. Operator build on Fedora they just have to make sure that the operator, the one they release will also work on OKD and will also be added to the catalog on you know we that we ship with OKD. Yeah, so let's get that enhancement request in get that you get it logged posted. To the mailing list when you do so that everybody can give it a thumbs up and you know vote for it. Yeah, the other thing that's parked that for a little bit. The other thing was the Azure images for Fedora CoroS. I sent around a tweet yesterday should try and find it again to try and get people to upvote that so that it gets on the radar. Do you think that this helps because I understand that Azure Microsoft already has a documentation page in preparation for Fedora CoroS. But the lawyers are talking to each other and I don't know if it helps to have a poll. If lawyers don't agree to each other. Since eight months. It's three years. Three years. Okay, nice. It's been three years of arguing between Microsoft and Red Hat. I don't understand that because it's it's it's yeah, it's the only major platform that does not support it. I don't understand what's the problem is. I think nobody understands that. Oh my God, like it's. Yeah, I think it doesn't make sense to talk about it because we cannot really change and we can't everybody knows about it. Yeah, all of us who have actually been burned by this problem all know the details and we can't talk about it. It's kind of a secret maybe maybe the solution is Voldemort I don't think because nobody is allowed to talk about it. Oh, I mean there's definitely some kind of taboo on it but like the best thing that I can the best thing that we can do is ask Diane to like poke somebody with a stick to make this like go faster but like there the amount of potential success there is so low. But that's the best we can actually do and I'm not willing to talk about it in detail while this is being recorded. That is I think I have a I have a nicer topic to talk about. Okay, completely completely different. I'm, I'm desperately searching for a place where we can collect training material for for OKD, because I think there is a lots of people who made videos block entries but everything is spread spread around and I. Yeah, I would like would love to have a place where we can collect that I know that we must curate it entries will get old. I think the idea is that we would revise OK DIO to actually pull this off because I know Diane you've been working on adding a couple of sections to OK DIO for this sort of thing. So that might be the right place to put it. Yeah, so we had the week talked about this a couple weeks or a couple meetings ago creating a side page for cookbooks recipes. I didn't get to it. I went on vacation instead. But I'm happy to create that landing page and have, you know, whoever helped work with me and do that and give you guys some access to editing that page just like Joseph has done for me in the past. Yeah, because that's I think I think that's that's where and I and I love the I love reading back the cookbooks and recipes because I'm an old Python person. So, yeah, yeah, so that I think that's where I would like to see it live if people are okay with that. I'm actually totally fine with that. Yes, me too. So I'll put that back on the menu for the thing. I think I had it on the menu. I don't know where it went. I'm just super happy that we now have open shift install create cluster and that actually works now. That that's the part that I'm so very happy about. Yes, it would be nice if we would have a big, big button as it leads us to a different page where we can collect links and this would be fine. So it's not so spread around everywhere. I see your name is on this too. I'm just going to put it towards the top that I remember to do something about it between now and next week. So yeah, this is this is something that it's near and dear to my heart to and creating it in a way that it's updatable. Maybe a YAML file that's easy for people to add things automatically and just put the link in and a description. Something along that line. So just give us a little bit of time and we'll figure that out and start thinking about what it is that you'd like to see there. We may have to create a couple of templates so that there's some consistency in what we're delivering. But yeah, and part of it is, is also everything that we just did yesterday. I want to find a good home for that on the OKD landing page too. So maybe an okd.io videos page or deployment, whatever. But anyways, we do have to do that and I my graphic skills as everybody knows is from MS paint period of time when I spent time with MS paint. I know there's probably a Fedora equivalent, but I missed that. But yeah, I'm not a great artist here. So yeah, any help that people want to do or mockups of what it might look like would probably be helpful. Wireframes appreciated and then we can figure out that. So let's start a side project on that. Maybe Charo and Joseph and I can think about that. Yes, for sure. Move that move that forward. All right, so we got 12 minutes left of what was supposed to be for me a very short meeting. And it obviously means that I'm not downloading any of yesterday's videos. So I'm not actually moving anything forward at the moment. Is there anything else that we should talk about? And I would just ask once you have the update from Clement Christian. Could you post something to the working group so that we don't wait two weeks to hear what the next step is? Yeah, yeah, I think we should maybe start off that process. I think it's a new to find a date because I think the doodle thing was met for for this week. This week is happening. So this week ain't happening. So I'll just tell him and then I may just write an email to him, Matt Dorn, Michael Rivnak and you Diane and Vadim to make all our internal folks. Set up and then we can kind of include J Dobies and Josh Woods to the course. I'll put the names in here. Yeah, if you could send me the names again, I'll just send out something like I'll do that tonight so we can hopefully plan something this week and then publicize that in the coming days. Yeah, all right, I will do that. Okay, if I could. On the subject topic is anything happening with the samples operator, which is still failing if you don't have the full secret that actually caused my recent update to be in a failing state. What the container six stuff is supposed to help fix. We don't have anything to put in there that that's kind of the problem. I mean, you don't have to load the samples operator in. I don't know if we can change the default setup so that doesn't get activated, but it's not actually required for a functioning okay D system. So not just not prevent an upgrade if we remove it or set it. It doesn't, it doesn't force it back on. It's only installed by initial provision but once you remove it it or disable it or whatever. Everything stops caring, because you didn't break anything. It just, it'll just update what's already present. What I did versus samples there. Yeah, I'll, I'll, I'll post in the chat or are you on slack. I've got a little shell script I put together that when I deploy one if I want to get all of the templates that the samples operator would load, I extract all of those templates, then cherry pick the ones that I care about. And then change the, the container link to one that it can actually retrieve without a secret and then and then manually load those into the main space and they show up in the catalog. Yeah, you feel like that should be done automatically. Yeah, yeah. But there's a workaround. It's not fun and Charles is your rook still working with the latest upgrade. Yeah, I'm running 15.4.2. I think is, is what's running. Yeah, because I got this mysterious mess air saying that you know storage, not supported. For the storage operator it says unsupported platform for storage class creation after the update. Interesting. Oh man. Might be an issue. The man. Okay. You should file an issue on the okay to repo so that charo can figure it out. Yeah, thank you. I think charo you're the only one of us that has a functioning like wrote set up on top of. Okay, I'm living entirely off of emerald storage because I don't have money. Yeah, no, no, I set it up off of charo's blog and it works like a charm. Oh, you know, you know what I've, if you look at the, the iPixie branch. I actually need to push an update because I'm using a newer version of rook stuff now. So it may be that if you're still using the older version of rook stuff that's included in my GitHub page, that might be the issue is there may be that broke with a newer 4.5 and that older version of rook. And I based it off of your, your GitHub page sort of, you know, suitably changed for my configuration. Okay. But that was like a couple of revisions ago. Living on the edge. I'm, I'm up to my eyeballs in new employee training for the next couple of weeks. They gave him the red hat already what else did you want. Right, I mean like you you skipped like so many things that I heard other red hatters have to do first so you're clearly done and ready to go. I did mine in like two days eight years ago. Like it was like hey, look at you. This is open shift. Have a hat. Bye. Bye. Here's some beer. It was much more than that. It was more than that even. But it flew by. So I think I was on premise and rally for two days. Then I flew back to Canada. Anyways, I do have to jump. Today at here, I sent you the email Christian and I CC'd charo and that team as well. So to start the thread internally with the operator framework training training people. They may all barf over it now that I've volunteered them all, but they've been told. So we should be able to get something going pretty quickly with climate. Again, we'll see everybody in two weeks, but do pay attention to the mailing list. And if, you know, if we get something in earlier than two weeks from now with comments set up, I doubt that, but we'll, we'll just make another call and add hot call. All right, can I let you all go. Yes. Thank you. And go back to just lacking with the coupon people now. All right. Take a wiped out from yesterday. Still tired. As you all should be. Yes. Thank you. I woke up early for that. That was a little surprising. Yeah. Okay, Brandon. Nice to see you all here and keep on keep on okay being. Thank you. Thank you very much. Thank you. Take care. Thank you. See y'all. Bye.