 I know Christian and I was just going to touch base with everybody. I was getting Christian, Vadim and Charo queued up to record a talk for the OpenShift Commons gathering and from what I can tell from the Slack. It didn't happen this morning, but you've got to reschedule date within Trado tomorrow. And I saw the slide that came through and the, you know, we're going to do whatever demos you want to do, but also incorporate a demo of deploying or using the CR, the code ready container. And that was that'll be part of the OpenShift Commons gathering, which is going to be on November 17, the first day of KubeCon North America. And stay tuned. Today is my day to update the schedule for that event. So I will add all the speakers to that and shoot a link to that out as well. I wanted to tell Joseph that I finally uploaded the past three OKD working group videos to the playlist. So I think I'm missing two others prior to that. So I will just keep going back in time until I catch up to myself and I apologize for that. And Christian, since you're here, I don't know how long you have. Do you want to give a quick update on anything that's going on with OKD, an engineering point of view? I don't see him in the list. He disappeared. Okay. He didn't come. All right. He was here for like a second. This is what happens, you know. He has said that he's having a horrendous meeting clash day. Yeah. Vadim's having internet issues. So it's not a good day out there in the internets today. I'm just going to say this. I'm going to go back to. No, it's not. I mean, today my camera broke and my computer decided that all of its USB stuff would break and I spent the last half hour trying to fix it. So yeah, today's been a bad internet day. So while I'm still yabbering on and before we jump into some other things, I have one more challenge hopefully to share with you guys that I would like us to and I talked to the folks who are running this. I hope all of you realize that the OpenShift console can be customized. If not, talk to me and I will put a link to this whole slide deck here. I think it's here. If not yet, I'll put that in the chat and stop sharing for a second. And I just wanted to see if I could get a few of the OKD working group I asked and it's okay if you do enter this contest. The link is in this presentation and boy. So it's a short on ramp. So by the end of the month, but there's a competition to show the best OpenShift web console customizations using OpenShift for mechanisms. The most I've ever done to the console is change a logo. So I am not going to enter this contest, but I'm going to throw down a challenge to see if we can get a little more visibility of OKD by having someone who is deploying OKD out there to share whatever as part of this. And, you know, you will win a cool OpenShift hoodie, which someone else will have to figure out how to drop ship to your house. And if you if you're interested. I have failed at that, as we all know, however, we are getting them, we are getting some swag for Commons and OKD put into the cool stuff store at OpenShift at Red Hat, which means hopefully by Christmas I can send you all present. Yay! Or for OKD for but that is a process and it is not I obviously I'm not in marketing. So I don't know it, but this is this deck that I dropped in here. If someone could check and make sure you can see it. If not, I'll make a PDF version of it available. It just walks you through all of the new features and what's coming down and it's really cool. And, you know, lots of good stuff around the console and getting started. So if you're, I don't know at Datoneal, if you're using any of this stuff to make it look wonderful or at BCIT. Bruce, if you guys have students who want to make a cool something. Well, we hadn't thought about branding the OpenShift deployment, but now I'm thinking about it. So there's. You too can figure out how to change the logo. That was all I figured out when I was. I always had my own logo for it. So I knew I was in my version of it. That was that was my my signal. So, so there I've done my duty. I've promoted the contest and that was that was that. The other thing I was going to say is, and I didn't find out the date and time of it yet, but there is birds of a feather hour long slot that we've been allocated by the powers that be at KubeCon or OKD Working Group. So, as soon as I do that, I will and if you win the console project, maybe we'll, we'll, we'll demo that too, but there's, it's an opportunity to do an introduction, probably repeat the same slides that we're going to use in the offering and do outreach to the Kubernetes community at that event. So that's, that's a really big deal. So we'll, as we get closer to it, we'll figure out how to structure that day and, you know, showcase all of you guys who are best abilities. So I don't know if there's any feedback yet on the code ready container, if anyone's used that and downloaded it and tried it out. I tried it on, I tried it on Windows, but I did not succeed. It was for some reason it blocked and on OKD on the issues page. Some other guy has also reported the same on Hyper-V. I don't know what the problem was. I did not investigate that much into it. And of course that's the one platform I don't have the ability to test on. What Hyper-V? Is a Hyper-V the one that's the problem? I think so. I can see that CPM is booting. I see some locks. Also see audit locks, but that's all. I see the exact same behavior on a Windows 10 Hyper-V deployment as well. Does it support VirtualBox as a hypervisor? No, CRC doesn't know. That's a shame. Well, it uses LiveMachine, I think. So I don't know. There might be a way to get it to, but it's meant to use the Hyper-V hypervisor. LiveMachine used to support VirtualBox, but I think they ripped it out because of bugs and annoyances with it. Because I know that the Docker on Mac used to use VirtualBox, and that was powered by LiveMachine. Yeah, and they switched out to HyperKit, I think. Yep. Did you say there was a problem? What? Did somebody say something? Sorry, was there somebody referred to an issue being open about that? Could you drop a link to that in the chat? Yeah. So I'm looking at the LiveMachine code or the Docker machine repo, which is where the LiveMachine code lives. VirtualBox is still there, but it, yeah. So the VirtualBox driver is still there as well as the VMware ones, the Google ones, the Hyper-V ones, all the other ones. They're all still there. Okay, well I think the CRC code would have to be modified to use it, because it's like a stretch thing, but yeah. Yeah, no, because you have to change your code that pulls in LiveMachine to use it. Yeah, yeah. I mean, my guess is, from looking, I mean, I don't know enough to be able to give too much of a guess, but it just looks like the VM starts and whatever the communication needs to happen between the external process and the VM just never quite happens. It's like it literally just gets stuck on creating the code-ready container VM. It creates the VM, the VM starts, and then nothing happens. I haven't tried leaving it overnight. Yeah, that wouldn't be very useful, would it? Do you know, are folks having the same issue with the Red Hat code-ready containers? I don't have a license, so I wouldn't know. I've been trying to figure out what the licensing is for Red Hat code-ready containers and have not gotten an answer for that, so I haven't touched it. Yeah, it's a little, I think it's a little annoying. If you set up a Red Hat developer account, you can use code-ready containers for free, but you have to create a pull secret from your Red Hat developer account. I kept getting access denied whenever I tried touching anything, which was like, oh no, you need an active subscription to do this. Yeah, for me, it wound up generating OpenShift eval subscriptions, which is not what I wanted. 60 days. So I reached out to my Red Hat account person to ask, like, what's the deal here, because this is directly opposing what DRC is documented to do and what code-ready containers on Red Hat developer says it's supposed to be done, and it basically blocks people from actually using it. I haven't tried the Red Hat CRC because I can't run it because it keeps creating evals or eval subscriptions, and I can't do that. Okay, I found there's a ticket somebody opened. Sounds like CRC stops working after CRC start on Hyper-V. So is that for the Red Hat CRC? Yeah. OpenShift one or just for the OKD one? No. It looks like everybody. Yeah, that was opened at the end of July before we had ours. Yeah, so maybe I don't see anybody from that team, even though I entered there. Is it working for folks on Linux and macOS? Last time I tried, it worked fine for me on Fedora32. So I haven't tried on 33 yet. I'm actually honestly a little scared because the changes to how DNS works by default make it so that I'm a little unsure whether the Libert DNS things, hacks that CRC uses will work. I haven't tried yet, and that's on my to-do list. But it worked in 32. Bruce, you said you were using it on macOS. Yeah, I installed it using, I guess, on top of the Docker driver, and it worked fine. Although I don't have, I've only got 32 gig of RAM, so all these things that eat RAM gets a little bit slow, so I'm not currently using it. That's sad to say you've only got 32 gig of RAM. I only have 16 or 24 on my different machines. It's a real struggle to run CRC. It's kind of bad because that's directly opposing the guidance which says, you can run this with 8 gigs of RAM. No, you can't. It doesn't even start with this default setup. Well, I think the docs claim it takes 9 gigs of RAM. Oh, really? Okay. I mean, MiniCube is small, but I don't even use that really. Go ahead, Diane. So that sounds like something maybe, yeah, it's okay. My internet is a little wonky, so you'll see my face pixelate, or I'm seeing your faces pixelate every once in a while. So that's just me and the wind is blowing outside my window. So that sounds like it's not on the CRC or OKD. That sounds like it's a CRC deeper issue, so maybe we can talk to Praveen about whether anyone's looking at it. Is he or Gerard or one of the team members, which brings me to the other topic that we had for today and I was going to try and book meetings for everybody. But holidays intervened, but we are going to try and get code ready into or OKD into the build process. The CICD build projects that's getting, so that Charo isn't building them by hand. And so that's our next ask. And I don't know, Charo, if you've had any more conversations with them. I think it was on me to set up a meeting with everybody and I have not done that because my schedule didn't permit it. So I think I'm the roadblock on that. Is that correct, Charo? Yes, it is. I have had some more chat conversations with with the code ready team. So I've gotten introduced to several people to actually one of them reached out to me when they stumbled across my repo. So we got the conversation going there. The other thing we need to we need to figure out, which is an internal red hat thing is branding for our code ready containers. Code ready is a trademark, kind of like Jboss or OpenShift. So we'll have to come up with something to call it. We can say it's it's based on code ready containers, you know, like we say OKD powers OpenShift. Oh my God, are we going to have to come up with a name for this now? Let's create a poll. Diane has one. Oh, yeah. I think we just flip it, flip it and call it ready to code. I'm good with that. I'm good with that. We're done. We're done. Nice. Got it. If you're good with that. But I'm also going to push back and say that this is branding that we should get permission to use code ready. So I will have a conversation with the powers that be because I think, especially if it's in the build process and it's, you know, it's part and parcel of it. And we, you know, I know internally at Red Hat, I'm having conversations with the developer evangelist team that wants to use more of this stuff in their, their evangelizing and getting onboarding people. So if it's called something different, that's going to not make them happy. So I'm going to see if I can get a little internal leeway to use it. So that was part of my hesitating on book booking all those meetings. I wanted to have that conversation with PMs first. So I'll work on that. But if you guys are okay with ready to code. I think that's fine with me too if we end up getting pushback. So that was that. So I'm wondering the other piece of work that usually I ask Christian to talk about is where we're at with getting the operators for OKD aligned. And I don't know, Charo, if you have any update on that at all from Christian and Vadim. I have seen some chatter around progress being made, but not enough to give a real update. But maybe it helps to know that people outside of this circle are thinking about it now. Christian wrote something about that. There are lots of internal talks about the operators, how to handle them, how to get them on in the community catalogs. And I would be interested in which kind this talks are. Are we allowed to do that? How does it get into CI? It would be very interesting to get a feeling about what their direction is. That is discussed. Is it completely clear that they get published or not? I'll see if I can get. Yeah, what I'm going to do is I'm going to ask Christian and Vadim. I'll talk to them today in Slack or anything to put a little update on the working group list and see if we can get that. But the goal would be to have it just be part of the build process for OpenShift to also push them out to a catalog for our use rather than having to rebuild them. So that was kind of my goal. And so I'll see if I can get them to do an update. I apologize because I think it was a very long last minute thing that Vadim and Christian couldn't come. Yeah, and they have to coordinate. You know, it's the same effort that we're doing right now with code ready containers. Multiplied by the number of operators because every operator has its own team, its own CI setup. In fact, there's not even unfortunately a standard pattern for how these operators are assembled and built. Right. So some of them might be built with helm at their core. Some of them are built with a container registry written and go with their core and others follow other patterns. So it's probably going to be a bit of a slog. But I have a good news. We made a workshop, a three week workshop with OKD and three, I think, main operators, a serverless service mesh and the OpenShift pipelines. We built the OpenShift pipelines on our own and also the serverless from the good repos. We did not simply mirror redhead images. And yeah, the first days worked rather smooth. The problem was not that the operators did not work, but that the examples from the trainer did not exactly match the version. But this is no big thing. It even worked in an offline environment. So in theory, it looks very, very great. The problem is that we built it on our own from source and my boss does not like that idea to publish that in the company. Despite of that, we have launched the OKD forecluster for our company today. And now all our people can work with that. It's rather stable and it's working in an air-gapped environment and so on. And I would love to have these OpenShift pipelines operated in the catalogs that we only have to click on the button. But I think we are not far away from that, as far as I understand. Yeah. Hey, and actually the screen that Diane's got now, that's some homework that I still need to complete around the pattern for the recipes. Probably get that done toward the end of this week. But with that said, Joseph, I've actually got now some working examples of doing a disconnected install with community images for the operators for RookSef, Open Data Hub, which you see on the screen there. Pipelines with all of the cluster tasks and serverless, Knative. This was actually a project, an internal Red Hat project that I stumbled into because some folks reached out needing some help with some stuff. And it turned out it's a client that is in a very, very highly disconnected environment due to the nature of their business. And they wanted to do a machine learning workshop, which needs all of those components I just referenced. So as I finish writing up how I made it work in their completely disconnected environment, I'll be using those as the pattern for our OpenShift recipes, our OKD recipes. Nice. And we'll write it. That sounds amazing, Charo. Yeah. Sorry, Diane. So hopefully we can start using this. That's OK. I just wanted to remind you this wasn't about prompting you to get that other one done. But I just wanted to say that we do have a space for this. And what I'm going to work with Charo on to probably this week, and we'll push a note out to the OKD working group on how, if you have another recipe, how to add it to this. Right now, each one of these and my internet access is really a little slow here. This one, they go to a read me file with the instructions here. So it's not, it's not, it's not perfect, but it is a way to do that and to filter it and everything is in github, github.com, and you just have to make a pull request. And we'll put the instructions in the OKD workspace. And it is very, very slow here. So I apologize, you probably aren't even seeing this. Yeah, my internet's are slowing down. Yep, you're not seeing this. Anyways, there'll be, it'll be in, yes, thank you. There we go. It'll be documented and we'll push out how to, if you have another recipe to add, how to put it in there as well. And eventually we'll get the, we'll make the site a little bit more beautiful than just linking out to people's individual ones. The question that I think Charo and I had still was if we, if we should be linking out to say Charo's github repo, or if we should be making a repo inside somewhere in the OKD.io repo or in another repo under OpenShift to put all of these. Those are the three ones that Charo has so far, but I'm guessing that each of you have others. Yeah, it seems like a good idea to put it under the same location. Yeah, otherwise people who want to bounce between them will go like they've got to go to this website for one, maybe there's something though helpful in another recipe that they want to reference. Absolutely. Maybe we should consider, I don't know if this has been thought about, but like maybe we should have an organization or OpenShift community stuff to be collected into one place. Because stuffing it all into the OpenShift github org is making it really hard to find stuff. It's getting too big as an organization. And maybe just having like an OpenShift community github org put all that in will make it a lot easier and a much more discoverable. Yeah, I was actually I was taking around the idea of something like the Red Hat communities of practice. There's an organization Red Hat-COP. We could have OKD communities of practice if we could create an organization OKD-COP. That sounds good. We could actually put the recipes there. And I think that would probably encourage more community participation, too, because it would be less of a barrier to somebody to submit a pull request to an organization than to, you know, my personal github account. Yeah, no, I don't want them all going into Charo's group. I was just, the other thing is to use the OKD.io github repo, but that's really just for the landing page itself. So yeah, thanks, Elmico. We'll see you later. So that's I think the communities of practice one sounds like a good idea as long as it's open and public and anyone external can create that can access and make a pull request. But for now, what I would say is if you have one that you want me to add into the current page, you know, for it, you know, maybe for any of the deployments that we did in the OKD marathon or anything along that nature or something else, just let me know. And I will, and with some probably coaching from Charo, link to it and we'll get it up and going because I would love to have a few more in there and to be able to reference that in the OKD working group presentations and at the birds of a feather in November and encourage people to do that. So we've got to figure out. I think the baby step is to link to wherever they live, if they're in your personal repos or in a data repo or in a roadie and Schwartz repo or wherever that's public and then figure out a home for them all. Well, I don't have anything public specifically for data, but like, I could probably look at some of the stuff that we've had so far and start talking about like if there's somewhere to put it, maybe putting it there and and having it public for people to see and contribute to. It's just there hasn't been a reason for us to do that so far because there's really nowhere to put it and nowhere to advertise. Well, yeah, and so I'm just wondering, I mean, like I'm thinking, and maybe I'm off the incorrect me please the digital ocean thing that Dusty made it and you did for the OKD working group marathon. Is, is that something that we could recipe eyes and available and link to and add in here is we could ask Dusty to see if it could be recipe eyes because if it could that would be actually really awesome. At least internally at work. Yeah, we have a semi ansibilized attempt at doing UPI installation on plain KVM. It is kind of working. But we also have like, we've done another recipe where we did UPI on open stacks or open stacks ridiculously old. And so the IPI doesn't work. So there's there's a couple of things like that that we've got floating around that we could possibly clean up and actually share. I'll need to talk to my colleagues about it and see what we can do. But like so far, the only reason I haven't really thought about it seriously is that we don't have anywhere to put it. Well, Jamie is. Is there a RIME I'm looking at your GitHub. I'm trying very slowly to get to your repub, rep. GitHub repo, but for that, the OKD OpenShift UPI script. Is there a decent read me file? Or is it just the code? Because I think the one key here is what I'd like to do is point to a decent read me file. That that's the only thing that explained how to a little bit. I think that's one prerequisite I would ask for is that what I'd like to link to is not the actual repo, but to the read me file. And I see your read me file there is just very short. So if you could look at maybe what Charles got, for examples in the Rooksef disconnected or the tecton one and just a little bit more verbosity there. That would that would be helpful because I might I worked on years ago at active state the Python cookbooks. And what they did was they grabbed like a little snippet of code or something it was a little bit more visual than what I have on the OK DIO site right now. And I'm just thinking that maybe my next step is to figure out how to show the read me file for each of these things or a snippet of the read me file. And some of that is what you're describing is also similar to the stuff that was written back for the the installation recipes from last year actually or earlier this year. A lot of those were mostly text with snippets of code and example and stuff like that. So similar. Yeah, but I think that's a good habit, or a best practice is just to give them a little bit. Yeah. And Joseph I'm looking at what you just clicked in there and again OK DIO. I understand. I understood that we said the idea is that we should have to create an organization and get up where we can put all repositories or forks and recypes in or any way we can start out. I think. Yeah, we have something. I'm not thrilled that the. Yeah. Well, OK, the communities that's cool. Oh yeah. That's cool. Sorry. Yeah, anybody. Maybe we can even move the OKD.io site. Anybody opposed to me creating that organization now. Go for it. I mean, I was going to create it until you just said that question. I think. Go ahead and create it, Charles. Let's run it by Christian and Vadim too, because I just don't want to offend the powers that be because we do have some community stuff in the open shift one. So there might be a sub directory under open shift slash community. This would be a lot less annoying if GitHub supported subgroups. Yeah. Yeah, that's the problem. It doesn't support subgroups. Which to get lab. Well, I mean, we could. I don't know about that. That's not the most unreasonable ask in the world. I mean, so do I put. Yeah. Yeah. So I think we have to be able to try the little carefully on this one because I. Yeah, part of me wants to take what's open right now the OKD landing page. I want to move it into wherever this is to so that it's not separate out there in open ship dash CS, which is. You know, community sites. Or something like that. Yeah. But I don't know the, I don't know the answer there and I think there, there is some, there's a little bit of politics internally about how we name the repos and stuff. So let's. Let's ask and then. I mean, the worst case thing is that the stuff that's currently in the open shift group. The worst case thing is that the stuff that's in the open shift group today stays there and we just have new stuff in the, in the, in the OKD COP or OKD community or whatever the heck we're going to call this because the real problem is that because everything's all jumbled up. It's a little difficult to find what we're looking for. Yeah, the reason I would strongly advocate for creating a separate space for these is that right now everything under github slash open shift is is really the ecosystem of the open shift product itself. Right, it's the distribution of Kubernetes it's it's it's what OKD is built from it's what OCP is built from. What we're talking about here with our call it communities of practice call it communities, you know, whatever we name it. These are the things that we do with open shift. Right, or it's, you know, it's our, our documentation our web page for OKD.io. That's the reason I would, I would separate them. Yeah. But there's also it's confusing because there is some community stuff inside of the open shift repo. So, I'm wondering if maybe we just create a GitHub repo that is the OKD cookbook and have recipes under it to start with. And as Bruce pointed out, communities of practice is an internal red hat thing too. So, I'm thinking OKD dash cookbook and then just leave it at that. And he just created it. Okay. All right, well, you're good. And let's, then let's do that. And then we can make pull requests there. And then that's what we'll link to in the in the OKD.io. Yeah. Yeah, I think that'll work. We'll see. But let's load it by, I don't think anyone's going to get offended by an OKD cookbook. And then then we can publish it as an actual book. And we can all make residuals and retire. Not that anybody who ever created a Python cookbook ever has gotten to retire. So don't don't bank on that. So cool. All right. Is there are there other things to do here? Yeah, I think Joseph. Yeah, that's I'm kind of leaning towards that. But let's let's let's keep chattering on on the group mailing list here. So let's get the first one done. If we can get that tecton one done this week and the documentation on on how what the best practices for linking to it and making a pull request. We'll make that we'll start making that happen. Okay, is there anything else on the agenda that we should do today or do we get 20 minutes back of our day. Everyone, this is Dimanshi here. I just wanted to. So basically from the K and I community team in Reddit and so we are trying to find solutions to easily deploy OKD on all all platforms. But right now I'm focusing on bare metal IPI. So there are plenty of options, but like we wanted to go with upstream ideally metal cube. But right now we are pursuing the script since that is much closer to OCP. I'm in like OpenShift and so basically there are also we try to use the scripts changed some images up to the upstream components and the rest of it. We had to use the downstream one since they weren't any available in the OCD group. So I mean we weren't able to deploy it, but we did achieve some success. So right now there is an issue open in OCD. I think that is tracking the images that are necessary to install it successfully and which might not have their upstream counterparts. So I'm working with some of the developers and community members to make that possible if we can build those upstream images. And from what I found so far, it looks like they didn't require that much work because they didn't have any dependency or like complicated those kind of relations that would require us to do significant work for them. At least some of them seem like there's some using some scripts and we could simply switch the image from rel to CentOS or any other upstream code base image. So I was wondering like if anyone is has any experience with something similar or are they working on some of that? Building upstream images for the downstream one switch are not available yet. First of all, I didn't quite hear and I apologize because my internet is not great today. Are you on the code ready team? Didn't quite hear where you were based. Oh, I'm part of the KNA community team. Can you hear me? KNA. KNA. I'm sorry if you are not able to hear me. No, I can hear you. I just don't know what that community is. I'm sorry, the abbreviation doesn't ring a bell. Yeah, so it's given it is native infrastructure. Oh, KNA. KNA. All right, sorry. Oh, that's what we've been talking about. Yeah, I'm so good. There we go. Oh, it's fine. It's just gaps in the internet making like the words get kind of cut off. It's okay. Yeah, mine might not be the best of both. Yeah, so basically like. Yeah, so basically the idea was to have some ups easy to deploy upstream solutions. So as a first step descripts, sounds like a good idea. That's an upstream project. And since it's able to deploy open shift without like it like with a bit of work, we should be able to use it for OCD as well. But the major issue we are hitting is the missing upstream. Images and which is why like it's failing at the bootstrap as space basically. So right now like we are working towards having a process where like we have available upstream images for the new releases in OCD as well, particularly cluster API bare metal. I didn't see maybe we are just using the OCD as well. I don't know like how we are doing that in OCD, but but many of those had the upstream images available in metal cubes repository image repository. So that so but like few of them didn't have that and I thought like if we can build those and so. And another reason for descripts using descripts was like at least so first of all, I faced issues with the installer. Basically the default installer, which is for open shift doesn't work out well. And when I switched to the OCD installer, like I downloaded it from the GitHub release and try to use that, but it doesn't work out well. Like I downloaded it from the GitHub release and try to use that, but it complained about some missing plugins. So I ticked around a bit here and there and finally like went with building a new like installer from the Fedora chorus branch in the open shift installer, which I think OCD uses and so at least I was able to manipulate that problem. But still like the installation is not going to 100%. So I've I'm tracking that in a document and I'll see if there is anything maybe I drop a mail into the OCD working group regarding the update. Yeah, we actually have an open issue right now that we're tracking to get those images from the from the RDO team. That's that's what you're running into. That's what we're waiting for because right now the images that are in there are just stubs. So we need the ironic images built from RDO. I'm going to drop it in the chat. It's issue 197. Yeah, yeah, I am aware of that issue. So but I was just like exploring like if I can make it work just like even if I have to use some downstream images, but like it just wanted to see like if I can make it work with their scripts because I thought like that is a good option to keep in mind because since like OCD and open shift are very close in the code and like within their components as well. So like with I think with small number of changes like with some parameterizing some of the environment variables and dev scripts like I think we should be able to make it work with OCD as well. And if that is possible, then we can use dev scripts for both of the projects instead of a separate repository for OCD. So that would and yeah, because so that's why like I yeah, so that's why like I wanted to make it work like have a successful solution so that I can pitch to the maintenance of dev scripts that hey like I we just need to parameterize these few variables and we are good to go for OCD as well. So then I can just submit a PR or few PS and that would be a good option to have because working with metal cube to be honest would be a difficult at this point at least because even with vanilla Kubernetes, I had issues to be especially in bare metal. They did like bare metal more or less has many separate issues. But anyways, so I thought like first let's work with dev scripts and then we can think on further steps. So I will send out a mail to the OCD working group regarding a brief update regarding this and where things are at and. And that sounds too to me like something and correct me if I'm wrong child that would make a great recipe as well. Oh, that's yeah, absolutely. Once it's working. Yeah, and it'll make it easier for it'll make it easier for us to maintain bare metal IPI. If we don't have to maintain separate pieces of code. I'm going to I'm going to send you an email so with my contact info. Sure. Thanks. Manchuk and forgive me. Are you a red hat or an IBM or where are you landing your. Yeah, I'm in red. Okay, I thought I've seen your name someplace else before that's okay. Oh, I had. So I guess you might. No, I mean, like a pep started the conversation, but. So you might have following that. So that's where I know you. Yeah, I knew I'd heard your name before and chat it. Okay, cool. And sorry about the the internet connection. It's not you. It's me. I'm in a wonky place today. So my internet's not great. But it took a few minutes with the CNI, but not CMA and like, I don't know that acronym. Perfect. All right. So that's where we're at today. Is there anyone else hiding on this call with a secret agenda item? Anyone else. All right. Go. Just that. Okay, go. I've been. Yeah, the, we focus on operators, but the, the various, you know, images and templates are also useful. And I was playing with some of the, the old samples operator ones that I saved as per Charles suggestion before I turned off the samples operator. And they, there, there are some that give you the option of using community resources. I was playing with the my SQL one. The, the only difficulty that I ran into is that, and I don't know how generic this is, but it doesn't give you the option of using the storage class. And, you know, the, the, I wasn't able to get it to work with my Rooksef, which normally automatically deploys. And, you know, if at the point that we get the samples up and running again, then it probably wouldn't hurt to go through those and look for annoyances such as, not being able to use storage classes. And I haven't, because I was sort of like, I don't need that right away. And I've got databases to work fine, which is what I'm going into next with my class. But the, you know, it for the long run, you know, there's a bit more bulletproofing that in bits and pieces, although I would be happy just getting the samples operator back, which Vadim promised in 4.6. Okay. We'll see. I'll put the samples operator back on the agenda and ping him and see if we can do that. I assume with the samples operator, it's actually possible for people to customize, right? Like it, like we can set up our own samples to be shown in there. Does anyone actually know that? I don't know. Well, you can always, I mean, you can always add in a image stream or a template by hand anyway. Yeah. So like I've got wildfire in my catalog, because I use that extensively. And I've dropped in a couple of databases. Yeah. So for me, for me, I'm looking at the idea of we're starting to build essentially templates for how application should be the environments that application should be developed in along with the databases they'll be linked with. And so I was thinking that samples operator might be a good way to make sure people can use beyond the happy paths very easily. Right. Yeah, definitely. So the sample operator back on the agenda for next time and I'll ping Christian and find out what the status of that is. Anyone else got a hidden agenda item for today? All right. You only get back five minutes of your day. And I put the registration link for the console competition. If you, Bruce, because I know you have students and they would love hoodies. So take a look at that. And I will BFI is the slide deck that explains it all and then post the link in that to the working group meeting in 20 minutes after I get another cup of coffee. Cool. And I'm very pleased to say my power did not go down. And if you could see the waves that are hitting the shore right now, you'd know that that was a miracle. So everybody, wherever you are, stay safe, enjoy. And we'll see you on the working group mailing list and or on the in Kubernetes and Slack. And so just reach out if you don't hear from somebody who promised you something, which usually is me. Yeah. You won't be able to see the slides, Bruce, until I get permission from Serena who built the slides to share them. So that's going to take me 20 minutes and a cup of coffee and a few bribes. I think Serena is a little easier than that. I think it's going to be okay with sharing the slides, but the bribes don't hurt. Serena already sent me a PDF copy of all of the slides. Yeah, bribes. Yeah. Yeah, it's out there. So I'll find it and put it on the mailing list. I think I've got a few because it would be wonderful if someone, yeah, that you've got them. I just have to put them in a place that I can link to. There you go. Speaker deck. Yes. I knew they were there somewhere. That would be great if we could get, you know, a number of people from OKD working group and maybe your class or whatever doing cool customizations. I don't know, make it look like a tick tock console. Who knows. We'll see. All right, folks. We never get in less than an hour. So I just enjoyed talking to you all too much and I talked too much. So thank you. We'll see you in two weeks or sooner. And I will also send out a couple of notes on some of the agenda items like the birds of a feather for Kubecon and when that's going to happen so people can, if you're going to Kubecon and sign up for that, because I know you have to have registered for Kubecon to get into that. So I don't think it's free. Kubecon is very expensive. Yeah, well, I mean, Lynx Foundation makes money that way. Yeah, well, somebody's got to pay for that platform. Somewhere along the road. But anyways, long story. Enjoy the rest of your day. And two minutes to the end of the hour. All right. There you go. Take care guys. Thanks. Bye.