 Everybody, this is Christian here. Something came up for me, so I have to actually run right now. But just to give you a very quick update, I've summarized the current state of the release 4.6 work in this comment. I just pasted the link to it in the chat. So that should be all open issues where we have right now. Unfortunately, it's still taking it's time to get the back parts in, so we can't release just yet. And there's one open issue we have to still figure out with regards to system gresolve d and that being active in Fedora 33, which we're now using. So there's still some ongoing work on that. The rest are really just back parts that have to go in. So that's it for me. I'm going to have to drop right now. Yeah, thank you all. And have a great meeting. Bye. Yep, you too. See you. It looks like Charles is the chair then. Yeah, yeah. All right. We can do whatever we want today. Only relevant update I've got is that there's a new version of Code Ready containers that I pushed up to the Fedora site where we're hosting the OKD Code Ready containers. And it doesn't require a pull secret anymore at all. So now when you run the CRC start, it will just start. It's not going to prompt you to paste in a pull secret, real faker otherwise. And obviously, as soon as we cut a 4.6 release, we'll cut a 4.6 release of our Code Ready containers too. But in the chat, hey, Joseph, I'm not sure how quickly those issues will be closed. I know one of the things that I think we're waiting on is Vadim is out on PTO. And I think he's the one that would close some of those and then cut the release. So we might literally be waiting for Vadim to get back from vacation. Okay. But isn't the local host issue still open? So Vadim was saying that was a blocker, that Fedora was changing local hosts to Fedora or something like that. And I guess that was, maybe that was on the CoroS group. Well, it's apparently a Fedora thing. So it's a upstream issue. Was it? If I can find it. Well, those are just really waiting on a cherry pick. I don't think we're waiting on any actual fixes as well so I can actually eat my lunch before my next meeting. Hey, my name is John Fortin. I want to introduce myself. Hey, John. So sort of taking the dive into OpenShift 4, we've been a OKD3. Probably 6 through 11 shop for about three years now when we're starting to look at OKD4. Got to test 4.5 cluster running and playing with it. But since I'm using open source stuff, I kind of want to get involved a little bit more than I had been in the past since I have a little bit more time now. So kind of wanted to get an idea of where to get started with you guys and what to do. I mean, there's always, well, you can do documentation and stuff, but I'm really more into the testing and implementation and trying to figure out what's going on type of thing. I've got a couple of open tracking issues going on and stuff and starting to try to help out with some installation issues as I can, but like I said, I just kind of want to get involved a little bit more and figure out where to go forward from here. Yeah, what kind of environment are you guys running on? What's your infrastructure like? So we're running vSphere, IPI. So my test cluster is three masters and three worker nodes. Had lots of fun over the last month or so trying to basically figure out, you know, the little idiosyncrasies of doing the installations and stuff. I think that the minimum requirements may be a hair low for OKD 4.5. We ran into issues where like worker nodes wouldn't start or only one would start, the other two wouldn't start and we'd run out of resources, start the second worker and then it would fix itself. So, you know, ran into a bunch of idiosyncrasies that are also things where they're trying to get ignite files for the masters and the workers and getting timeouts from this or that. From our point of view, that seems to be related more to the VMware utilization once we move things around. Response time dropped from 30 to 60 seconds to five to 10 seconds and everything installed. So those are kind of things that we're kind of working through and like I said, I've kind of opened up, you know, one or two, well, I guess one right now, installation ticket and, you know, with a, shoot, what's his name? Victor. Vadim? Yeah, just, hold on. I was just looking at it and... I pasted the link to the GitHub repository of OKD in the chat. Yeah, Vadim. So he and I have talked a few times and stuff. So like I said, I kind of want to get started and help out where I can and also help with testing and stuff because the one that helps me get better at it, especially since 4. is so different than the 3. versions. Operators are one of those things that are still sort of baffling the back of my mind. But, you know, I've got things to work like I've got RookSeph to work, you know, so I've got, you know, Seph working on my backend storage. So that's been good, but, you know, one of the things I've been working on today was Ingress. So it looks like the base HA proxy supports some Ingress stuff, but not great. Looks like 4.6 is going to be better. But part of me is wondering whether I'm, you know, looking at, you know, better off looking at a third-party Ingress controller rather than the default HA proxy controller. Those are the kind of things I'm working through. Yeah, yeah, because you'd like to use an Envoy. Or even something like, you know, the newest, you know, HA Ingress controllers and stuff, HA proxy Ingress controllers. So those are, you know, we're not ready going into production with 4.5 or 4.6 yet. We're still doing a lot of learnings. And I'm not comfortable going to production with it at this point. But yeah, that's why I'm here. Yeah, the way you've started is really the way to get involved. Joseph posted the link, but it sounds like if you're opening issues, already got that link to our page on GitHub. Really, but I would say is, you know, there's a lot of other vSphere user. I do a couple of things. One, you know, monitor the issues and feel free to add comments and suggestions to people who are having problems. Two, continue opening issues. And three, share your experiences. If you've got a GitHub page of your own, share some of your experiences with the other folks. And this is a normal bi-weekly meeting this week, or this meeting in the last one had been a little bit truncated, partly because of holiday schedules, partly because of- Yep. But I will say this group is pretty regular. This meeting here on bi-weekly Tuesdays can have anywhere from a dozen to 25, 30 people on it. So there is a core group of people, Bruce and Joseph and Neil and there's Neil speaking. Yeah, no, like my notification didn't go off so I didn't realize it. And then another meeting overlapped and then I was looking at my calendar and was like, wait, I feel like I should be doing something right now. That's okay, Diane, Vadim and Christian, all three blew us off today. So. Who's the guy with the guitars in the background? Oh, that's you, that's Charo. Oh, okay. Yeah, I watched one of these the other day and I saw all the guitars in the background and I was like, all right, there's a dude after my own heart. Charo just has an exciting setup at home. Yeah, I like it. I have a question though. I saw somebody mention something about the Slack channel for OpenShift. I tried to join the Slack channel and it got into a circular thing where it said you had to have an email to get an invite, but it was... Slack is horrible, Slack is horrible. Yeah, it was basically impossible to get a request or an invite. Can we just do Matrix or something? Like it's really, really irritating and really frustrating. Don't change a running system. Almost a running system at least. Let me see, is there a way from... As far as I know, Diane is the only administrator of the OpenShift Commons Slack group and the Kubernetes group is, she's the only one from the Red Hat side with administrative access to grant people invites into the Slack channel. Yeah, because there's no way to request an invite that I could find. No, for reasons, you have to know Diane and ask her first. And this is... I never had to do that. She pre-populated the OKD working group upfront in the very beginning. That's why. Oh, okay. Yeah, so like with... This is one of those things where it's like, we are supposed to be an open group where people can come freely to us and stuff, but we're on a platform that's actually literally designed to be closed off to the world. Like this makes no sense at all. And yes, I get it, nobody likes IRC. We have a better option now. Can we use that? Oh, Fedora is actually going to be getting a matrix server. They're planning on... So there was a discussion a few days ago and it's seemingly looking like what's gonna happen is that there will be Fedora server. There will be a Fedora project.org server. And I'm pretty sure Charo did not hear any of that, so that was probably a bad plan. UPS man just pulled up and the dog had a conif... I think everybody goes through that. Yep. I let him out so he could go bark at his favorite UPS guy. So Charo, what I was saying before you let your dog go bark at the UPS guy. The indications are good that Fedora will be getting a matrix home server and we'll be re-homing all of the IRC channels for Fedora onto there. That might also be a good opportunity for us to add a matrix channel, a matrix room for OpenShift and OKD stuff and start bringing people in as the open default platform for people to collaborate with us. We can probably have the matrix room bridged into the Kubernetes Slack for the Kubernetes community, but I'm really uncomfortable with the fact that we have been promoting Slack this way because it adds a burden to Diane among other things and it's just not a good platform if you're promoting open source and open standards and an open infrastructure thing. It's literally the antithesis of it. It can be a pain in the butt, that's for sure. That too. Also, I'm just getting real tired of Slack just pinging me all the time about everything. BlackBot is your friend. Hey. Hey, let me go back to John for a second in terms of right now we have Slack and that's the tool that folks are using. So John, if you go to the kubernetes.slack.com and try to sign in, are you able to sign in in general into the Kubernetes Slack? No, he says if you're a member and I say no so that I put in my email address but it wants to invite kubernetes. Hold on, let me actually go to it. Yes, that's confusing. Yeah, it was. That's Slack by design. Slack is not made for communities, it's made for companies. Right. Yeah, so I get going kubernetes on Slack and then it says continue with Google, try that. But it also says, or that's your email but it's your email at getaninvite.slack.kubernetes.blablabla. So none of that works. So when I try to go in with Google it says that I'm not a member. When I try to get an invite, I don't have an email with a getaninvite.slack.kubernetes, whatever. Yeah, that's just the thing to tell you to go to Slack.kates.io. Yeah, that's what you start. It'll try to generate you an invite about a quarter of the time it will fail but most of the time it works. Yeah, try that. Where was that? Slack.kates.io, it's in the chat. Oh, let me look. Cause I took a link from the okd.io when it brought me to that page. So let's see. We might need to change, we might need to. And if you have problems setting up okd 4.5 paste your questions there and we will help you, you're not the first one. This is literally the reason I hate Slack. Okay, all right, that was much easier. Woo, welcome. All right, well, let's see how that works. I'll check that later. Okay. But yeah, that other page, like I said, it was an infinite loop. There's no way to actually generate a request. That page has been broken for about a year now. I believe Diane tried to get someone to take a look at fixing it, cause I believe that's run by the OSPO team. But nothing's happened. And so here we are. Well, hopefully that'll work and I can jump in a little bit more. Like I said, I want to help, you know, what I found is that helping people also helps me learn a lot more too. Oh, absolutely. Yeah, that's why we're all here. I want to keep my brain active. Yes. With this whole thing, I need an active brain. I was going to say, with everything else that's going on, there's got to be something to do. So maybe it might be helpful while it's fresh in our heads to do a debrief of last Friday. Does anything stand out for folks that were there Friday? Does anything stand out in your mind from the Boff event? I was there. There was a handful of other folks. Anything stand out? Anything that you think you're thinking that it helped? It kept kicking me out. It kept kicking me out when I tried to join the Boff. Kept saying I wasn't signed up and didn't have, didn't have the right conference pass. So at some point I decided to give up. I think that was specifically, they applied a needle filter to it. Oh, okay. Well, that's fine. I didn't need to be there anyway. KubeCon is a boring event. Actually, the birds of a feather was the only KubeCon event that I went to this year. I went to a couple, but like a lot of the events I tried to go into, despite the fact I had like a full pass, it kept saying I didn't have the right pass to actually join them. And so I was like, after a certain point, I was like, all right, clearly this isn't going to work. And I don't need to spend my day like hitting a broken platform. So I kind of tuned out most of KubeCon because of that, which was unfortunate because that was the first KubeCon I'd ever been to, been to. And that didn't go so well. Well, I think one of the things that stuck out in my mind is that it seems like in a lot of discussions and also in a lot of the videos, the question comes up repeatedly, the relationship between R-COS, F-COS, and OpenShift or OCP and OKD, it might be helpful in the documentation to actually write out something for the OKD website or for somewhere near the recipes or something like that so that we can always just point people to a document that says, hey, here's the relationship. Yeah, and actually I think I'll try and remember to dig it out. I'm pretty sure we've got some old slides like a year ago where we were talking about exactly that. It goes back to some of the early conversations that we all had arguing about whether OKD should be truly upstream of... That was Neil arguing, really, yeah, but yeah. Hey, wow, I'm glad you remembered, Jamie. I think we wrote documentation where him and I wrote something on OpenShift, OKD, in one of the readme is about that. Yes, that's right. Maybe that helps. We should probably pull some of that into OKD.io. I've also, the whole OKD.io website is written in this cryptic ruby. Yes. Which, I mean, I would rather just write straight HTML. Yeah, please. That's how I feel about that website too, for what it's worth. It's not even like normal Jekyll. It's got some real funky stuff in it that just makes it real hard. Yeah, and it took me two hours to get it compiled. Yes. To engineer everything. And then I updated the Big Sur and that completely destroys all compatibility with the ruby version. So now I can't do any work on it at all. You should be using Linux. You know this by now, Charo. Hey. Just get a little big slap top. Hey, hey, for a Linux to Mac OS, I have like a 20 to one ratio of Linux operating systems to Mac OS. To be fair, I'm in the same bucket. I have one MacBook computer and then all the rest of them are Linux machines. But this is one of those problems. Just throw a Linux VM on there and call it a day. No, the right way to do this is to divorce ourselves from this crappy ruby thing and put together a subcommittee of the working group to rewrite okd.io. Yeah, by the way. Use something normal like Python. And re-occommiting it out is a crap. By the way, search on docs.okd.io is broken. Yeah, that's for a while now. Yeah. But, you know, we do have student projects. Like you can get a team of students full-time for five weeks for I think a $400 administration fee at BCIT and like that sort of rewrite it in some modern technology would be a typical project. That sounds like a good plan. Can we get like $500 to do that? I mean, we usually have a budget of zero. Well, it's in Canadian, which means 25 cents American. Oh, that's true. Right, yeah. I could throw a quarter. There we go. Not quite that bad. Diane's working on leading her Canadian citizenship. Well, we'll just let her. Yeah, Bruce, you ought to reach out to Diane. Well, if I knew that you had that project, I would because we're, I mean, you're dealing with students so, you know, there's no warranty, right? So you might get something, you might not get something but usually you get something good, just not always. We're open source, right? So we know what no warranty means. No warranty is the name of the game here. I'll tell Diane because she might actually be able to handle something like that as a commute. I mean, because her job is community. She might be able to handle something like that as sort of a red hat community project and get red hat to put the bill to reach out to her because that I was kind of half joking, but that's actually not a bad idea. Yeah, it's not the main problem, I think, but maybe after 4.6, after the release, we could do something with that idea. But this is to rewrite it, yeah. The last time I looked at the O.K.D. docs, they were full of, you know, R.H. cost references. So I think if you're talking about confusion, that's a good place to start too. Is there's, you know, like I haven't gone through and put in a ticket on it, but just because there's so many of them and life is short anyway, right? I just learned to ignore those. Yeah, so this is, it's actually the reverse effect that you find in a lot of the other red hat products. Like if you go looking in JBoss documentation for, you know, JBoss EAP, you'll find tons of references to wildfly, right? Which in my opinion is the way it should be because JBoss EAP is just a sub base distribution of wildfly. OpenShift still is suffering, you know, with the 4.release. I mean, even in the later 3.releases, it is like a, it's almost a downstream, right? It's not upstream at all. The Fedora Core OS is the only upstream piece of OKD. Now, I think once we get 4.6 cut, we will be on the exact same code base of all of the core operators for OpenShift code. The one piece that will still have its own F-COS branch a little while is the installer. Yes. So once we get 4.6 cut, there really is an opportunity for us to get in front of releases, because really OKD 4.6 should have dropped before the supported OCP. Hopefully with 4.6 going into whatever 5.0 is going to be, we'll have an opportunity just. We're leaving a 5.0. What the heck is going to justify a 5.0? Because eventually we're going to run out of numbers, right? That's not 4.99. I mean, we still have projects that have 0.1 point, like 50, you know, like 50 or something. Like that's a thing. Yeah, but we're trying to pretend we're adults here. Oh, oh, that's the new thing. I'm not. That's no fun. Charlie, do you know something about the progress for the community operators that are used also in Red Hat OpenShift? Because there was a restructure refactoring situation a few weeks ago. Christian told me that this was finished, the new package format for the operator. And yeah, can you tell us something about the state of the operators, the service mesh, pipeline, Tecton? Yeah, so for every one of those, we're at the mercy of that specific operator team to start conforming to that new format. So the good news there is that as they start doing that, we'll start seeing those operators showing up in an operator hub. So we won't have to wait for a big bang where they all get done and then suddenly, oh, we got all the operators. The bad news there is that any stragglers will have to keep pressure on those individual teams to get those operators into place. I saw a post about that at some point. I don't understand what the difference is between the OpenShift operator hub for the commercial product and using those for OKD. I saw something about a licensing issue with that, but aren't most of those operators open source? Every one of them is open source. Yeah, they're all open source. The main difference is that the Red Hat maintained operator hub, not to be confused with the community operator hub, is behind a paywall, a subscription-based paywall. In fact, you can go get the operator from any of the open source projects, like RookSef. Yeah, I've done that. So if you've installed the RookSef operator that you got from the GitHub page, you've effectively installed the exact same operator. The difference is you didn't get to go to operator hub and click on the subscription and click install. So it really is more of a free as in beers thing. It's freely available. It's just not as easy as to get those operators also in the unconstrained quay.io or the DNCF-hosted operator hub. In general question, we always have if the code base is really exact the same for the community versions and also the Red Hat versions, because there are some hot fixes. I think OpenShift users will get first before the community can get them or are also the hot fixes being pushed to the public repose. Yeah, so everything, everything that Red Hat does, all of the hot fixes actually show up in GitHub first. So the people that are paying Red Hat money, they're not getting fixes before the community gets them. What they're actually getting is fixes that have gone through Red Hat's testing QA and validation. So if you follow the issues, like say you come across an issue in your QBIRT operator and you need a fix for it. If you're monitoring the issues on GitHub, as soon as those pull requests hit and the CI system builds off of those pull requests, again, it's the whole free as in beer thing, you can grab those and get them in. I used to do that back in the day with JBoss when I was Enterprise Architect for Advanced Auto Parts. We were actually running Community JBoss instead of the subscription-based product because the subscription-based product is so far behind that it didn't support the newer JWE features that we were trying to implement. So for years, we ran Community before we started paying Red Hat subscriptions for EAP. And that's exactly what I did. I would just monitor the upstream and when a fix came in for a problem we were having, I would just grab the code, build it, and shove it in. Mm-hmm. OK. So would that be the operator store? I mean, is that a valid place to start poking and prodding to add some help to or something? One, because I need to learn more about operators anyway. But one learning how to build them and how to install them would probably be a good thing before I start getting deep down into the code and creating my own. We should start with the operator SDK. We did the same. And it's not hard to create your own operator with that SDK. It's much more easier than two years ago where people told us that this is the absolutely greatest king-size thing you can do on Kubernetes. It's rather easy now if you do it with operator SDK. Well, I remember watching videos from about a year and a half ago or two years watching. And I'm like, what the hell is this? People are actually doing this because it was so complex in terms of what you had to do for all the configuration files and everything. I'm like, whoa. No, you have to go with the operator SDK. We wrote, I think, three or four operators on our own in the last months. And it's very, very feasible to use as SDK. OK, everybody behave now. Diane just joined us. Yeah, I did it again two times in a row. Wrong time zone in my calendar. Speaking of operators and videos, I'm going to post in the chat this video. That's a really good one for operators. Jay walks you through the whole process. So folks that are interested, Jay and Chris Short do a great conversation about the operating SDK. Well, the nice thing about the operator SDK is also that you can very, very quickly peek into existing operators. And you will find everywhere the exact same structure to learn what the operator does. That's a great benefit of this operator SDK. And all operators are moved with that. But the community operators that we're talking about are they written mostly with the SDK or are they written with all the other tools that seem to be helpful? SDK, almost everything I saw that is related to OpenShift was written with the operator SDK. You see that if you go into, if you see a package directory, package controller, and there is a go file with a function called reconcil, then it's created with the operator SDK. And there you can find what it does. Yeah, that's the beauty of the operator SDK. We have also reverse engineered some OpenShift operators where the documentation was a little bit behind what it's already doing. Yeah, I've had to go into code for a couple of things in OpenShift to try to figure out what in the world is going on, like what version we're actually running, and what you get, what you wouldn't get. What actual commit that's built it was so I can go look at the right source code. I did that today with the HA proxy thingy, because there's no documentation to it. As to what you can do with it, what annotations, there was nothing that I could find. I had to go into the code. That's very annoying. There's lots of operators that you have to look into the code, but the cool thing is, it's written in Go, not in C++. You won't have a very hard time in understanding what they do. Yeah, now on top of that, there are a couple of frameworks so that to create an operator, you don't have the SDK. Those frameworks are built on the SDK, so they're doing it for you. You can build operators with Ansible and with Helm charts. They are obviously a subset of the full capabilities that you can get with the operator SDK, but you will stumble across some operators out there that have been built either with Ansible or with Helm. All right, guys, I'm going to apologize for getting my time zones wrong again. This is two times in a row. I'm going to officially move it in my calendar so it shows up in the right place. And I put the link in for signing up and letting us know that you're here. And I have invited a couple of folks in the last time, Juliana and Mike, from the Advanced Cluster Management team to join us, to talk to us a little bit about using that in the context of OKD. And I'm not sure, because since I'm coming in late, whether I don't think they got to talk at all or did they introduce themselves even? And they want to unmute themselves, maybe, and put themselves on camera? Hey, Diane, no, we haven't present yet. Just give me two minutes. I'm going to say, oh, I closed everything. I thought the meeting was canceled. And then I'm going to present the whole thing. Cool, so that's great. So I apologize, folks, and I am now officially changing my time zones on the calendar. I did that this morning. Vadim is still on PTO, and Christian had to go to something else. So my question to everybody, since I'm late, is did I know Vadim is on PTO? So I'm taking it the 4.6 didn't get out the door. No, no, the Christian posted a list of everything that's holding it up. So there's a link actually in the chat. All right, cool. So I think because I joined late in the chat, I'm not sure I get that link. Let me just see there. I just reposted it. Thank you. Let's take a look at that. And I'm sure you all discussed everything on this list and anything we could do to make it disappear. But is it all dependent on Vadim coming back? There's a couple of PRs that we're waiting to get accepted by their respective teams. And then Vadim or Christian to cherry pick those into the MCO. And there's potentially one Fedora Coro S33 issue we're waiting on resolution for. And I'm just going to use that needle. Is that the one where we have the wrong IP table so everything just breaks when it tries to configure networking? Yeah. That sounds right. Yeah. Someone reported that on Twitter. It was like, oh yeah, OpenShift is incompatible with itself because Fedora Coro S ships the IP tables legacy and OKDX and OpenShift expects IP tables NFT and everything is busted. Like, oh, well. Great. More fun quirks caused by our PMOS tree. Is that here in this list anywhere that you mentioned? I don't know because this is the first time I'm seeing the list. OK. So the link is in there. So if we need to add a comment. There was also one. There was also a problem with the local host and Fedora user. I don't know because it's also open, not closed. But it's not in the list of Christian. Is there an issue somewhere that you can add in to this? It's on this page, a little bit above. Oh, OK. Yeah, if it's already in there, we can add a comment. You might ping it with a comment to see if that is still an issue. They were talking, I think, today about that. If you follow the chain of the issue, then someone was saying sorry for something in a different ticket. What was the number on that issue? There. It's Christian, go down, please. OK, tell me when to stop, basically. Yeah, yeah, yeah. Coro has 649 when you're talking about. It's something about network manager, local host, Fedora. It's from Christian. It's a short one from Christian on this page. Is this one here? This one here, OK. Yeah, I think this one is a problem. Oh, looks like there's a temporary fix for that. OK. That may be why it's not in the finalist down toward the bottom. Is that number 2160 there is probably the stop gap. I just threw a link into the ticket. I just added a comment at the very bottom about the Fedora Coro-S issue, about it having the wrong IP tables implementation that has been tracked in the Fedora Coro-S tracker. But we need to add it to our list to make sure that they fix it with OKD46 going out so that OKD46 doesn't do unexpected things and get broken. I'm doing these thumbs up not because I like them, but because then I know where I was when I was talking about it. Right. To be clear, the reason why this is a problem is because REL8 and REL Coro-S use the NFT implementation of IP tables. And so all the software has been written around it. And the legacy IP tables that doesn't use NFT doesn't support enough features for everything to work. So some clusters will come up, but others won't. So I've seen some issues with IP. Some people have complained about IPI deployments failing because of this. Whereas, UPI deployments all work because we don't do any network configuration in a UPI setup. So is it the wrong IP tables? Or is it that Fedora Coro-S is using the legacy IP tables in the tape? No, no, no. It's that Fedora Coro-S is accidentally not using the latest IP tables. They're using the wrong implementation. It's a regression. Yeah, it's a regression. Not intended to do that. Yeah. OK, so whose other fence is that on? Is that something the Fedora Coro-S folks have to? That's the Fedora Coro-S side has to fix. Yeah, we could probably ping Dusty with that one to find out status. Can we? Sounds good. I just wanted to make sure to bring that up so that you all know that that is actually a problem that people have been reporting. Yeah. Yeah, we could put in Dusty Maeve on that one. If you want to talk about ACM, here's the GitHub link to the community GitHub pages that upstream. I think that's all the pieces that make up ACM. So I'm going to stop sharing for a minute and get Mike to introduce himself. And the open cluster management folks are here, otherwise known as ACM. So I thought that we've been trying to get them on the stage for the past couple of meetings. So if we could use the last maybe 5, 10 minutes that we have. That's perfect. Thank you, Diane. So hi, everyone. My name is Mike Ng. And I'm a software engineer with Wethap focusing on the product called Advanced Cluster Management for Kubernetes for ACM. Today I want to present to the OKD community what we're doing in the upstream project called the Open Cluster Management. So there's a lot to talk about. I'm probably condensing and now talking to quick 5, 10 minutes overview and quick demonstration. So let's get started. So what is Open Cluster Management? In Wethap, we have the enterprise offering of Advanced Cluster Management for Kubernetes. And OCM, Open Cluster Management, is the open source backbone of that project. The project is really about Kubernetes and how to manage multiple Kubernetes clusters in a consistent way. So multi-cloud obviously is becoming more and more of a reality today. And we want Open Cluster Management to be the go-to solution on solving some of the challenges that multi-cloud management raises. So how does this all ties in with OKD? Well, through the operator hub, users can install our OCM solution, cluster management operators, and multi-cluster subscription operator onto the control plane cluster, which we call the hub cluster. And then the OCM agent clusterlet can be installed onto the clusters that they want to manage, which we label as a managed cluster. So I'm going to do a quick demonstration on how you can use the hub cluster to deploy application across your managed clusters. Mike, can I ask you a quick question? Is that, did that come from the operator hub.io or from the Red Hat operator hub? Operator hub.io. These are upstreams already, and you can install them with OKD, and not just. Wow, cool. That's awesome. I want to play with this. One other question before you continue on that. Is there a website that talks about the community cluster, open cluster management thing? Like I just quickly popped into GitHub, and I couldn't find a website for it. Right, we're working on launching our website. We have the community here that talks about all the goals that we're trying to accomplish. And then we also have, we're working on launching our website. That's going to be launched real soon, and then which we'll give like an overview of. Basically, we phrase it as some of the community mission statements that we have here. So any more questions before I continue with a quick application deployment demo? Roll on. So I have the OKD cluster here on the left representing the hub cluster. And then I have the managed cluster on the right representing the managed cluster. So in the interest of time, I would register the managed cluster to the hub cluster. So now I can do things on the hub, and then they will propagate down to the managed cluster. So the first thing I'm going to do is a quick deployment this manager's work. The manager's work is a CRD that we define. So we can push workload down from the hub to the manage. So and then to show the managed clusters, we also have a CRD that we define as well, which shows, hey, this managed cluster is connected to the hub. So when I apply this manager's work, and then on the managed cluster side, and in this workload, I'm just deploying a small config map. So I'll see the config map shows up. And so this is a really quick example. And now I'm going to show up a little bit more complicated scenarios where we want to deploy a Helm chart from the hub. And then to have it propagate down to the managed cluster. So this uses application lifecycle management, which is another open source product under the open cluster management umbrella. So it uses a subscription model. So we define where we want this subscription, where we want the application subscription to be placed at. And then once it determines where it's going to place that, and then it's going to push the subscription into the managed side. And what it does in this particular subscription is I'm trying to install an Ingress app with a version 1.41.2. So in each of the managed clusters on the hub, if it's registered, you'll have a namespace. So in this case, it'll be a cluster 1. So when I look at the status of the application subscription, so we can see that it's placed onto the status AO, I found the placement rule is this placement rule. Sorry, there's so much details. I'm skipping some details. So placement rule is placing where the application should be deployed into which clusters. In this case, it found the cluster 1, which now is this propagated. If I go on the managed side, it'll deploy the same subscription. So this subscription is a standalone subscription for each managed cluster. And then we can see that all the Ingress is now deployed on the managed clusters. So that was a quick demo concluded. And we're really seeking feedback from the community to help shape what goes on in open cluster management. For example, this was application lifecycle, but there is also a cluster lifecycle. And how do we deal with the policy and configuration across multiple clusters? How do you deal with the cluster health? And all of these four areas of the open cluster management is trying to address. So please take a look and join the conversation in the community repo. And we'd love to get your direct involvement or bring your organization and get more directly involved. We'd love to have that type of participation. And that's it for the quick overview. Yeah, that was very quick. And thank you. Can you pop over? Can you share the screen just for the record and go over to operatorhub.io and show everybody which one of the operators it is? Yeah, give me a second. A couple of questions. There's a lot of naming conventions in this. The product side of this is ACM. The open source side is open cluster management, and I think we've named or you've named the. So does it also come with the web UI? Because I remember that there was a web UI. Is it also included? Right, so part of the process of transforming the ACM to the OCM is we're going to slowly open up open source our entire stack. So right now we only have the foundation pieces, the API that are open. So for now the UI is not open yet. But will it also be transformed, Mike? No, what do you mean by transformed? It'll be open and then you'll get almost the exact same feature set similar to OKB to OCB. OK, so you mean the web UI will also be open in the next time? Yes, we're working on it. OK, great. It may take us a while. We're doing one of the components one by one. And once we get all the components open, then we'll do the UI as well. That's great to hear. Thank you. Thanks a lot. It's kind of like CoreOS. ACM was a proprietary product under the IBM umbrella. And it has been open sourced, but they're still going through the process of getting all the code out there. And so that's why you see some pieces of it that I haven't coded for yet. But it's great that we can expect it in the future. Let's put news. I'm really looking forward to this. This is going to be exciting. Thanks, everyone. Awesome, Zos. All right, so I know when I talk to Juliana and Mike earlier, they're also looking for people who want to participate in their community as well. So that's going to be an interesting group of folks to work with, too. I think what I'd love to see is once it gets a little bit further along, maybe we could record a video of it running on OKD and do some demos and do a briefing on it again and whatever you need, really, is we're here. So. Yeah, and guys, it's intended to run on a management cluster, which could easily be a single node cluster on the OKD. So you don't need to stand up another full OpenShift cluster. Or if you want HA, you could do a three node master worker cluster. See, I think this is where things get very interesting because literally one of the things that I've been talking to to some of my coworkers has been we want to provide a way to do something along the lines of an OKD as a service for developers to spin up a cluster, a tiny, tiny cluster for the purposes of doing microservice oriented development. And the challenge right now is that it's such a pain in the butt to actually orchestrate the setup, deployment, and destruction of Kubernetes clusters, never mind OpenShift clusters. And so this is something that I'm really excited about personally. And once, as you guys get further along in this process, it'd be great if you came back and gave us the full presentation that you intended to give rather than this sadly shortchanged one that we unfortunately had this time around. Now the tower is going up right. You guys can come back in two weeks. I'm here for the next hour. I now have a free hour. Wait, you get a free hour? Yeah, except I'm working on my boss's presentation on this side. So yeah, it's a free hour except I'm multitasking, so it really isn't free. But if you folks could make a brief, I know Diane, you've in the past scheduled where they did a recording and made a brief, and then you just straight up uploaded it to YouTube to show that off. If Mike and Juliana, I don't know what your schedules are right now, but if you want to stay on and do a deep, I can record it. We can just record it as part of this. And I don't know what your schedules look like. Are we showing them to Juliana? Are we showing them to ACM or just AOCM, the open part? We need to show that the parts are just open for now. And then as we gradually open it up, we can share more of the details of the components that are open. Yeah, I'm not sure if I want to do it. Yeah, what we can do is we can put together a video. Mike, our community hasn't been created yet. We're grudged. You get a sneak preview because we haven't started yet. That's OK. It's fine. I'm excited. I'm pretty sure all of the rest of us are excited too. Yeah, so I think that the other thing that I would say is if you do put that video together and do a write up about deploying the operator on OpenShift, we have a recipe section of our OKD.io site. And that's where I would embed the video into there and link to whatever write up you guys did. So if you want to record something and make a read me file specific to OKD deployments, that would be a great thing. So if you go to OKD.io and you'll see in the nav bar a very limited set, shall we say, of recipes so far because I'm still working on everybody twisting arms. Somebody needs to work on that. Yeah, I don't know. I created an organization. I haven't done anything with it since. All right, well, that does bring us to the end of the hour. And again, I apologize for everybody for my time zone issues again. It is now in my calendar at the right time. And so in two weeks time, we will meet again. And is there anybody else on the call who I know I have the community? We've still got a few people here. Sure, some of you ready to jump. Is there anything that we should have talked about from the projects page? I'm just going to look at that really quickly for a second. Oh, I know that. Did anyone come from the Red Hat actions team? No. Is that the power 64? No, that is the GitHub actions. Sort of the get off side of things. There's a movement of foot inside of Red Hat and collaboration with GitHub. And I think I'll try and get them to come to the next meeting if they're not here today. I don't think they were here. There was someone from the IBM Red Hat partner power team, but they disappeared a little bit ago. OK. And that was Alexis. Yeah, and then the other thing was the key lime stuff. So I think that, as long as I didn't blow off anybody from GitHub, I'm happy. I'm blowing all of you guys off. Wow, we had fun. Because I knew Charo or Vadim or someone would show up and have my back. So anyways, so next time and two weeks time will be the date, so it's working into the holiday season. So that would be the 8th of December. And I actually may ask Charo to actually host this or Vadim or that because I'm in an all day meeting on the 8th, 9th, and 10th, and on the 10th, which is actually 10th. It was so terrible that they scroll you away into a three day all day meeting. Oh, there's two at the same time. So I'm into it. That's even worse. Two of the said, there's a staff meeting for three days and then there's a pragmatic marketing, product management, training thing at the same time. And on the 10th of December, but in Japanese time, which is actually the night of the 9th of December, or the night, something like that, something weird. We're hosting an OpenShift Commons gathering in all Japanese. So if you have any Japanese friends, it will be gonna be a fun adventure for me hosting an all Japanese event. So yeah, that's all right. So I may not be here for the next one. So I will, I may sneak in, but we'll see. So Charo, you may be on tap for that too. So let us know what special guests we're expecting and we'll cover. I will reach out. It's a gentleman, his name is John Bonahan from GitHub. And I will ping him again. He's going to do a briefing for me anyways on January 4th on using GitHub Actions with OpenShift. And this is sort of like, yeah, I'm pragmatic enough. I'm gonna be cranky on that day. And he's gonna do something on January 4th and they asked to come in because I think it's something that I wanna see if it's anything of interest for the OKT group. And that would be another thing that would be a nice recipe to have as well. There you go. All right, everybody, we've run over seven minutes, which seems like the shortest meeting I've ever had with you guys. So thanks again. Take care and we'll see you soon enough. All right. See you soon. Thank you. Bye. Thanks, Mike and Juliana. Bye. Bye, y'all. Our point six is coming soon. We'll make a big hullabooler about that. Can't wait. Yay. Yay. Get Vibdine back. Take care, guys. Be here.