 Good morning. Good afternoon. Good evening. Wherever you're healing from welcome to another special cube con EU 2021 edition office hours today. I am joined by members of the wonderful okd community I would like to thank all of you for joining today And I'm actually going to have to probably turn my video off at some point so that all of you can fit in the Screen if you end up sharing anything on screen. So thank you very much for joining and watching I'm going to hand it over to Josh real quick to run about introductions and Josh take it away Thank you. And I'm here welcoming the okd working group our community for okd the most exciting distribution of kubernetes And let me introduce the members of our community here and we will start with dian Hey Yes, sure As we all are recouping from a late early morning or whatever you were at cube con. I'm welcome all I'm dianne euler. I am one of the co-chairs of the okd working group. I'm also the director of Community development at red hat and okd is one of my favorite things on the universe and I'm really pleased here to have today a number of folks from the okd working group so that I don't have to talk too much and most of them have had production home lab All kinds of different approaches to deploying okd. So please pepper them all with your questions There's lots of good Experience here with okd And I'll hand it over to chero. Maybe now Hey everyone chero groover recent new hire to red hat actually been with the company for Oh goodness about nine months now August will be my one-year anniversary So I've transitioned from being a 20-year customer of red hat products to now being on the other side of that fence and subjecting other customers to these wonderful products been using okd since the three dot x days actually used it In lab settings as well as in development and experiment environments that that eventually led The company that that I was employed by from becoming a an ocp an open shift customer So I'm very excited about seeing the journey that a lot of you are taking with this Sort of upstream side stream project that is my favorite kubernetes distribution by far And I'll hand it over to jamie Hi, I'm jamie magara. I'm a dev ops engineer at the university of michigan and I have been utilizing okd for some time now as a development sandbox for developers at the university of michigan And have done a lot of work in automating installation of okd UPI v-sphere installations And have done a lot of work in trying to Improve the documentation and make it more accessible to folks such as the viewers here who want to embrace okd And let me pick now joseph Hello, I'm joseph mayer. I'm a cloud architect at the company rhodie in schwarz sir German I'm unique located company. We are in a telcom and I'm Using okd since more than three years now We used it for starting our digital business journey And we used a lots of distributions before okd And yes okd was was our favorite ones in our evaluation phase We are using it for our development Engineers and also we use it in production currently Few hundred developers are on it and it has great potential for us. It Yeah, we I love it a lot and I worked I work with see together with the okd working group. I think since more than one and a half year now In yeah fixing bugs testing testing a lot in my homelab here mostly on v-sphere but also I did a little bit of work for asia and I select John Hey everybody So my name is john fortun. I work for a company called market america. Um, I've been using okd since it was origin back in the day probably about three dot four Uh, we are using in production currently in 311 and since about October and november of last year. We've started to really look at okd 4 And starting to do a lot of testing with it. I've been involved Quite a bit with the testing on v-sphere, especially ipi Bug smashing squishing You know trying to get Okd 4 to be as stable as we can possibly get it for the the best amount of people So it's been a lot of fun. I'm really enjoying this community And let's see who's left Timothy Timothy Hey, so hi, I'm timeterre avier and I work in the chorus team as a software engineer at trade at And essentially I do a lot of the work On federal chorus that's needed to move the the OS forward And that's mostly it for me And for folks that don't know fedora chloro west is the underlying operating system that the nodes of okd utilize Yeah, and I think we need to start out because We're having this during kubcon. We have some people who are completely new to okd So does somebody want to take on the usual question, which is what is okd? Why Yes, I think we do and in fact we've got some material to share on that so without further ado Let me Share my screen You guys should be seeing an okd working group office hour slide. Give me a thumbs up All right, okay, so what is okd? That's what we're going to talk about here. We're going to give a quick overview Give you a quick update on current state where we are Talk a bit, but not a lot because we'll save it for some of your q&a about what what differentiates okd and open shifts from some other kubernetes distributions and Finally give you some info on how you can connect with The working groups both the okd working group and our fedora core os working group so okd It is a community distribution of kubernetes end of story that it is a Distribution of kubernetes. So it is 100 percent kubernetes Right, this is not a fork of kubernetes or something slightly different. This is All kubernetes That that's a question that we get from time to time It is also open shift. So so any of you that might be red hat subscribers to OCP the open shift container platform The code base of of okd is the exact same code base as open shift The difference is that where ocp is sitting on red hat core os as its underlying operating system We have an upstream component of our open shift distribution that is fedora core os So what does this provide for you? Well, you know, it it is a kubernetes distribution like we described But we also sort of refer to it as a kubernetes plus plus Because it automates a lot of the installation the patching and the updates From the operating system up. So once you have your open shift cluster up and running It is going to take care of itself to a great extent you you can have zero downtime updates although A lot of us tend to cross our fingers when we're doing the updates, especially since we're running upstream but By and large the the updates are a very pleasurable experience Except on those rare occasions when they aren't And like other kubernetes distributions, it enables you to run cloud native applications from a host of Programming languages platforms the the technologies that you would expect to run in a cloud platform Without locking you into a specific cloud provider So whether you want to run on your own metal you want to run on Overt or open stack or vmware or aws or azure or gcp or a host of cloud providers Your applications will run the same because they're running on the same kubernetes platform So The state of where we're at right now is Version 4.7. So so we are at parity with our Subscription-based ocp 4.8 is going to introduce some exciting new capabilities that we're all looking forward to to trying out in our labs Coming up here pretty soon One of the ones that i'm most excited about is going to be boot strapless single node clusters Any of you that that have worked with deploying an open shift cluster at this point You know from one of our okd projects You know that that one of the first things that has to start up is a bootstrap node that exists only as long as it Takes to to get the cluster up and running Well for single node clusters with 4.8. They are going to be able to bootstrap themselves I don't know if any of us have experimented with that yet. I know that I have not I hope too soon But that's something i'm really excited about We're also getting a lot more collaboration now Really starting in our 4.6 release, but it's accelerating in our 4.7 release With a lot of the providers of the operators that you find in operator hub So more and more of the operators that are available in the subscription based product Are now showing up as their upstream counterparts in our operator hub There are also providers that are Starting to create new operators bespoke operators for okd And and this is giving us an opportunity to to really enable adoption of Upcoming and newer technologies like i'm in my own home lab I'm running upstream versions of seth for my storage provider for as a tecton So that I can get a feel for you know new things that are going to be available in Open shift pipelines or open shift container storage as they come along I'm going to talk for just a minute about the operator pattern because this is one of the things that that really differentiates okd From other kubernetes distributions is that from the bottom up okd is based on operators the very first thing that starts running on that bootstrap Know to get a cluster up and running is an operator Operators manage the entire ecosystem operators Control the updates they control the versioning they control and maintain the health of your cluster So from the the the cluster version operator, which is the thing that is controlling all of your top level All the way down to Managing the underlying operating system the version of fedora core os that is running on your nodes Those are all operators Which makes the care and feeding and maintenance of one of these clusters Much easier than what you may have experienced in a more traditional kubernetes environment And again, like I said operator hub is the place to get just about anything you want to run in your cluster And as we continue to work with our companion projects that provide the operators for The ocp platform you'll see more and more red hat official operators showing up in the operator hub as well as a host of community provided operators Finally, I'm going to introduce you to Our working groups so that you can connect online with this very active and very excited group of individuals We'd love for you to come and join us I'm going to leave this screen up for just a little bit so you can screen shot it or snap it or whatever Uh, this is our our slack channels our google group We have bi-weekly meetings that you can find at that fedora project calendar site And we maintain a couple of repositories Uh that we track our issues and features and and things of that nature again fedora core os by the same token and i'll leave this slide up for a few seconds A few seconds again Has a very active community And timothy is here with us today. So if there are any fedora core os specific questions He is the man to answer those for you Here are a few more resources that you can grab I'll leave this up for a few seconds for any screenshots And because this is an office hour and not a slight presentation I talked very fast and blew through these slides. So let's get to the office hour and answer your question Thanks everybody Okay, so we have questions all over the map um from both existing ok to users and from I uh folks who are looking at it because of this Um, one of the first ones that came in here was from sanjay um Who is interested in using dns mask? um I As a service or something else For caching dns inside okt um and wants to know If there's anybody's experience with that if somebody has put up a how-to somewhere Thoughts that one may be a dumper I I have not um, I have not Attempted to do anything with that yet I'd be interested If if he could type it in asynchronously and what the specific use case is what the need is for a dns cash Um, because I have it personally in my lab or or even in the production ocp clusters that I that I've worked with come across a scenario Where the native dns provider of the cluster itself? wasn't sufficient Okay, I've asked him to expand on his use case Um, so we've got some other more sort of basic questions about installation Um, one was somebody who wants to try out okd Um, and they're having some issues with the installation being complicated Um earlier you talked about the boot strapless Um installation that's coming Is that is that sort of your me our main installation simplification effort? You know, it's the beginning. It's the beginning of it right now If you're installing okd on one of the major cloud providers And this is true for okd and ocp The open shift installer itself Is able to natively communicate with that cloud provider Um, the I I'm going to I'm going to speculate that the individual asking the question is probably doing a user provisioned infrastructure Install what we call a upi install and those those are um somewhat more complex because they require Uh some upfront configuration of you know dns providers networks things of that nature that that are you know that that Add complexities rather than just running open shift install and then answering a few menu questions and watching your cluster grow in aws or or gcp or azure Yeah Yeah, you know where i'm going so, uh, we have a uh off the website, uh, if you go to okd.io there's a link to a A series of guides that cover aws, azure, gcp Home lab single node v sphere and these are guides for upi A lot of upi some ipi um For installing okd On these platforms and so that Is a great place to start if you're running into issues um Check it out because there's a lot of the sort of the nuance detail that you might not find in in the um The standard documentation standard okd documentation and it provides some background on prerequisites For example, that's really helpful. I think uh in the case of the v sphere upi. I've actually got a Repository with a script that does the whole process for you pretty much after you said a couple variables So, uh Yeah, good. Sure. Oh, sorry. Sorry jamie. Yeah, one of the things that I love about this group is that we're all lab enthusiasts But we're all running in different types of environments So so there is there is somebody in this working group that is running on Just about any platform that you can imagine So i'd say if if you have installation questions Join us in a working group meeting Uh, if we can't answer it We might ask you to figure it out and document it for us, but um Most of us have have written tutorials and how-to guides and things of that nature That that is jamie mentioned. We're collecting together so so that folks can can go find Uh An instructional for installing that is beyond the the documentation you find online And I I would just put a pitch in our next okd working group is um next tuesday at 1700 UTC And it's open to everybody and if you go to okd.io You can find the guides in the nav bar and you can also find the information to navigate to all the repos Latest release and everything else And hopefully find your way to the okd working group forum on google as well. I put that in the chat earlier That is a great place to post Questions as well, and we are really active in the kubernetes slack in the open shift dash dev channel So if you get stumped Go there. There's usually somebody there, but it is i'm going to say community supported. So this is a not a red hat technical support supported thing so And the the good news is it's a really active community and as you can see by all the folks that are here today As well as we've got great great collaboration going on with the fedora coro s folks Because I really do want to emphasize okd runs with Fedora coro s as opposed to rail coro s. So it is a very different. We'd like to say sibling Upstream or sibling stream to okay ocp But we want to emphasize the community aspect of this one And make sure that people are fully aware that all your help and efforts To get support and answers is going to come from the community We are a group of volunteers That's right. Hey one thing I can say with installation is that you can make it as you know easy as you know A 20 or 30 line configuration file to as complex as you want it to be I run ipi so pretty much. I have a set of One configuration file that I can repeat over and over and over again And if I have to change something it's just a small tweak You know jamies is probably a little bit more complicated because of what it does with the hcp and All sorts of other things but it can be easy or can be complex and most cases are going to be in between Yeah, I'm on the other spectrum With with custom ignition files. Yep What else do we have for questions? Well, so speaking of complicated installations One of the people in chat actually wants to know about air gap installations. Do we have a guide for that yet? okay, yeah, actually the Tutorial that I have for a large cluster actually does cover doing an air gap install. It's upi Based jamie. I don't know in vSphere or joseph Have either Sarah talks for air gap installations on also on vSphere Yeah, yeah, so several of us have done have done air gap installs Mimicking, you know a real data center environment where you you don't just allow internet access straight out Okay so Here I take a look at that and if you have follow up questions you can ask them later on Um, the um our our dns sanjay just got back to me. He's basically He's got services that make heavy use of dns And he's looking to not overwhelm core dns In his infrastructure for application dns requests And also maybe get better response times by I guess having pods that are local to each node I'm doing dns and was wondering if anybody has any advice there I related to this since it's a community on chat user stephan actually said That they are using node local dns Um on top of vSphere with their cluster Okay That actually sounds like something some of us would be intrigued about so I would say please join us in a working group meeting if you can because I think several of us would like to experiment with that type of Um scenario That might be a good topic for the discussion group in the in the github now too. Yeah, it might be a good one to be able to put some stuff in Yeah, because I'm I'm sure we we could come up with different models to to achieve that Even you know the dns mask running in a container that's that's locked to nodes. Um is an interesting one Yeah, I guess a lot of it would depend on why it is you want this extra level of dns Right, is it because you really really care about lookup response times or is it because you're modifying the dns all the time? Right, because those are two different use cases The um, okay, so that's a your answer sanjay is please follow up with this On you know the slack channel or in a github issue or something people are interested in it people have different ideas on and and feedback about different ways to do this the um If somebody wants to give seven some links again about how to join those forums Um other questions, uh, there's some brief things. Um, I Actually, here's an important thing also if somebody can post another link somebody wanted a link to the slide deck So if somebody can post that in chat um the All right, here's one of the other questions, um, which anybody can feel really quickly One of the chronic problems with installing um upstream kubernetes using the official kubernetes testing images is that you often find yourself disabling sc linux Um, somebody want to confirm that that is not something that you have to do when you install a locati That is not something that you have to do when you install okd I would say third and fourth that We highly discourage disabling sc linux or your firewall. Leave your firewall up to yeah The um Okay, uh More sort of questions. Um, one of our uh chat people actually wants to know whether or not there are Packages or installation scripts more likely I for installing it on sent us stream Um, I guess the answer is probably no because we need fedora coralesce. Yeah Uh, if if they mean that they're underlying hypervisor provider is sent off stream um, I just updated my lab environment to sent off stream the Operating system of okd though is fedora coralesce And and we don't we don't support any other operating systems currently other than fedora coralesce running on the master nodes in the compute nodes Yeah, so basically the just to give a little bit of background on that there's a machine configuration operator and different parts of okd that talk directly to the os and and manage the updates um, and uh, they're pretty tied to each other And so there's more documentation on that on our website But um, if you want more nuanced detail on sort of how they're all connected Feel free to to pop into the channels or look over the document Yeah, and currently if i'm wrong, um red hat folks I believe even on the the the subscription based site for ocp. We are moving away from um Supporting non coro s nodes as well. I know we we used to support rent rail nodes for compute nodes But I think we're even getting away from that I still think you can use rail for worker nodes now For seven now. Yeah. Yeah But whether or not that stays I don't know You you can for now, but the for sure the the main the main ones we want for the master node at least we We enforce with that chorus and that's the priority the the one we're putting the most focus on So A couple other things one thing is All of these community things. I just I want to call out We had a question in here another community manager answered it, right? Which is somebody asking is there a way to install okd on poxmox as a virtualization platform Yeah, someone else actually jumped in in the chat and said they've already done that. So Yes, um, it was my first installation doing just that. Yeah Cool. It was my first installation for okd and it works. So pretty good. Also on poxmox Cool. Okay. Um, here's a more uh, technical question, um, which I'm going to read out directly because Which is uh, nils wants to know is the okd ipi process the same as the ocp ipi process They're using okd ipi as a test platform Um to test a migration from upi to ipi installations Um, uh on vSphere, um, and they want to know when they do this in production. Can they use the same process for ocp? Yeah, I've done both So I took my configuration file for uh okd And with a couple of very small tweaks to make sure I was pointing at the ocp stuff work like a charm Okay, I think you can even use the same. Well, I don't know I used I used the the ocp installer and the okd installer I'm not sure if you can switch those out and have them installed, but the process itself is the same In my experience Okay, the um Which point are you looking at? Well, actually some of it, um, I'm going to rephrase this because it's you know, um Go for it. I don't want to trash talk anybody, but the um, one of the things is so one of the questions right is would okd effectively Be comparable to rancher in terms of of when somebody is looking at use cases Hmm, I will admit I haven't used rancher I think I think uh open shift is or okd is more opinionated Than rancher, but you at rancher you have to take care about more things So it's always a trade-off Yeah, rancher has a you can You you can install anything you want on open shift or okd You can install anything you want on both But um in a opinionated Distribution you have to take care about less stuff Yeah, somebody mentioned The amount of Resources needed to run okd. I think that once we get to that single node okd For people use You know, you'll find testing wise will be able to do a lot more for a straight install of okd You know, even for testing It's still fairly beefy. You have to have fairly beefy nodes So that's one of the things you have to keep in mind with whatever distribution you decided to use is Do you have the utilization or the resources, you know to be able to run it? Yeah, the the trade-off there is that you know that all of the automation and self healing that comes with okd right that does require compute and and so So okd is uh a bit fatter from its resource requirements than you know a plain Vanilla kubernetes or or another container supporting platform But the the the trade-off is a self managing environment that that really gives you a cloud native experience in my opinion Absolutely, which is one of the reasons why we chose it. I don't have time to manage, you know every five minutes, you know the the cluster Um, I can turn over a lot of stuff to my developers They get a lot of authority to do things within their projects and I don't have to manage it. They can manage it themselves That's one of the things I just love about open shift and you know okd Don't forget the web ui Yeah, I would echo that. I think that you know from the dev ops perspective that's sort of okd and open shift provide uh that sort of Middle layer that's really good if you look at some of the other container orchestration options out there they involve a lot of glue scripts and Stuff that you have to bring to the table and I think okd provides a lot of that And makes it very easy for developers to sort of slide in to the role of Of a container developer and dev ops. So it's really good. I think for that transition Of getting developers into dev ops And for sysadmending it. Yeah for sure. Yeah, and with the maturity now of projects like rook sef and cube vert You know, which which also have productized Versions that you know that you can get subscription support for I mean my goodness you you have a full hyper converged cloud native environment that That can replace most of what you find in a data center I'm a bit of a fan Um strong a strong point we have with okd is that so that's my federal chris hat on That we test the full os the full everything that comes with the os with everything in the okd platform So what you get is when you update from one version to another of okd You get the platform which has been fully tested and to end The os and everything on top of it and you'll practically show that everything works together Which is like something that only happens in okd in ocp platforms Cool And as long as you're in muted timothy, uh, there is actually a question specifically to you somebody is actually looking for A primer on how rpml history works Sure, so rpml history it's is um the company the main component of uh federal chris node and that helps us manage versions of the node so When you update your okd cluster you update all the components of the kubernetes components And you also update the nodes at the same time And to do that you use rpml history and what it does is essentially rpml history is A git way to manage your operating system So you move from one version of the other of your federal chris node And you you just pull a new image and and you essentially reboot to it To update and so that has a lot of advantage advantages So that the first one is that we actually test all of those images We have several streams in federal chris and we make sure that they work And then the second one is that every single update you do on your system is atomic And it just either happen or does not happen at all So you just to date into the new version and that's it you're done So you've got progressive rolling updates on your cluster to make sure that you're always up to date With the latest version of the nodes cool, um Speaking of latest versions Uh somebody wants to deploy an okd cluster using Reddit using advanced cluster manager Now we we just had The ocm office hour an hour ago. So I actually know something about this now, but Does anybody anybody have firsthand knowledge? Not yet I I will say to stay tuned Unless some of you guys have have used it a bit because I do now have Two clusters running in my lab that I'm going to put a cm in front of But I haven't gotten there yet. So in a few more weeks, I'll have an opinion And I think a cm is also one of the operators that will be available also for okd Soon say it's a promise to make it available for okd ACM or ocm ocm is the upstream Yeah, I don't know. I just how it will be called but yes, it's upstream. Yeah, okay ocm is the upstream project of acm for those of you You don't know and it's we're open sourcing all of that and you can find it What I think this is a great topic for in maybe a future office hour to demo this bit because um, the folks from one team Have been reaching out to the okd teams And uh, would like some airtime too. So I think there's going to be a nice bit of collaboration there Yeah, we might we might wait on that until a hundred percent of it is working though Minor detail Yeah One of the things I would say The benefit of the okd working group is we are on the bleeding edge Test all of this stuff for people. So if you have a new project or a new operator and you want it tested Come to the okd working group because we we love being guinea pigs Maybe not for some of your production environments guys, but um, I know that's one of the things That's really useful the upstream open source side of Open ship is to get stuff tested over by the okd working group And we do bleed on occasion And to test experimental stuff like somebody actually wants to know suggestions for edge load balancers Um that people are using with okd I'm going to be quiet, but I can't um, there is um a whole sig around edge and working groups Um reach out on the okd Forum um in the google group and post that question and we will find the person who has the answer to that I don't think anybody here has really done that but we have talked about edgy stuff Edge related stuff and arm as well as arm stuff in the okd working group. So there are people who are Covering those topics Just not here today Okay, I know there's quite a few folks using like metal lb Yeah Yeah, um, which is still a relatively new project And and one of those things we should be doing more sessions about So people know how to use I don't know how to use it. I'd like to do a session for that reason Um, let's see a few things. Um, somebody's actually looking for best practices information Uh, particularly when installing on bare metal In terms of what they need and how to configure it So if you go to Go ahead. No, go ahead. Jamie Yeah, so there's so uh best practices. I think can probably be construed from the guides that we have Um, and the documentation we've actually tried to do although there's a lot of variety in upi Uh, and in bare metal in general, uh The guides actually have a Some good Practices outlined that basically you could determine best practices from those um, so we probably need a little more Uh discussion with that person to get a sense of their environment if they popped into the channel or something like that But you know, um, the guides are a good place to start. Yeah One of the things that I think to pay attention to Is the recommendations for memory and cpu on on your services Um, some people will try to run less Sometimes it'll work sometimes it won't Those are probably Uh, the best way to start is you know, is with those as your minimum requirement Once you get a cluster working you want to try something else, you know, go ahead But you know start with with the minimum requirements and go from there Yeah, that and avoid spinning discs for your master nudes. Yes At cd Like disc latency No, like there's there's a whole article that uh talks about that ibm put out I'll grab a link to it real quick, but that's a very salient point Oh, come on. I used to run a demo with at cd running off of five usb keys You could do two maybe even three writes a minute Yeah Yeah, your cluster is going to be just fine. Yeah Is that on your ck modem? Yep. Yeah. Yeah Hey, listen, um, one of the areas I used to consult was actually, you know Department of energy power generation, etc Um, and the onboard computers they have on power equipment Uh, all of these are actually real hard work constraints. Unfortunately The but we have questions from the audience actually on specific features. They're features that like they know from ocp and the supported versions They want to know what the equivalents are on okd One of them is Container native virtualization Um, so the the openshift virtualization feature and the other one is service mesh um So what do those look like on okd? Service mesh, I believe the operator is in operator hub now for service mesh Really? Okay, I think I'm looking I'm looking real fast to see if um Because last time I installed both service mesh and kubbert. I did it with the upstream operators Um, I know they're on our wish list Okay, so kubbert would be the cnv equivalent Yeah, yeah kubbert is the is the container native virtualization upstream And for service mesh you have a lot of different possibilities, but I mean, I'm doing the up the uh upstream of istio not the operator from operator hub, but I mean, they're good. I mean they work Yeah, my stress service mesh that uh, it's the it's community provided operator It's a community supported operator provided by red hat that that is in the operator hub for 4.7. I just confirmed So, okay My my stress service mesh Yeah, um, and so Uh, so people know some terminology. We know a lot of names here So one of the things that we do at red hat is we try to give the open source community Supported version a different name from the red hat subscription version so that people don't get confused um, and so For open shift service mesh that name is maestro, which is istio Plus the management tools and ui and stuff that we've developed to make istio easier to use I'm not sure that that keeps it less confusing or not, but um It does keep them separate in terms of support Availability, so I think that's really the key here. I yeah, I tend to think it just makes everything so confusing and we do have a catalog for operators for For okd. So if you go into the repo and Follow the links there you can find that and we're working on getting making sure we have equivalency with ocp And that they're all tested By the community. So that's that's one thing and the thing that I would say is we also Are really looking for a community participation in updating our docs So if you're looking at our guides or at docs.okd.io and you find something that's out of whack or not quite clear enough Login issue. We definitely will take any even grammar checking Helps us and and we really have had a great swell of testers from on all kinds of implementations and deployments of Of okd and it's really helped a lot driving innovation and getting ocp and the The product itself very stable. So it's really the engineers at red hat have been incredibly supportive of the okd community And you know shout out to fedeem and christian and you know timothy and other folks who have really You know a lot of their spare time Weekends and others getting releases out and helping the community move things forward So we're incredibly grateful for that support too, but this is really a very community driven effort And uh, it's you know any and all feedback and if you have some strange interesting contortion A stack that you want to write a guide about or if you have an alternative to one of the routers We've been using or a different way of doing dns just Hit us up In the the working group forum on google or in the kubernetes slack on openshift.dev We're all hanging out there most of the time and we're pretty global In our coverage. So there's usually someone on all the time That means someone gets woken up. So Speaking to community support. So we have a highly technical question in the Streaming chat. I don't know if any of you guys are actually logged into the streaming chat If not, we might want to recommend that he actually take that somewhere else because this is this is not something I even read aloud. It has network errors and stuff in it The yeah, I and and definitely looks like an occasion for community troubleshoot I would say if the person could take that to the channel or the email list that we have the the kubernetes net he's based a Slack channel that we have Open shift dev on the kubernetes slack server Or our email list either one of those then we can Take a look at it for sure Yeah, yeah, we try to avoid doing troubleshooting At that level during office hours because sometimes that means bouncing around documentation and Things like that, but we're happy to help for sure um More feature questions. Um I is there a way to do windows containers um with okd those container support I I think so Yeah, I thought that I thought that started with four seven That was the wrong In the okd working group, I haven't seen anyone's head pop up saying it but it is compatible with what's available to do in an ocp So Theoretically it should just work along with the same lines as the ocp documentation on it Yeah, I don't know if it's supported with upi, but it should be supported on ipi installations Yeah, the the the operator is available in the operator hub It's called the community's window machine config operator to to enable windows container workloads I haven't tried it yet Uh, but I can't confirm that the operator is there give it a shot and let us know I'll have to find a windows workload or try to run right So that's the thing is that netcode for me when we get questions like this Where maybe none of us currently in the group have experienced with and this isn't everyone in the working group Um, but if we don't have experience if there is a someone out there in the world who's asking us If you could try it if and and let us know how it goes That would be awesome because then we can write up some documentation We could point to your use case, uh, etc. So feel free to join us and and help us, uh, hash out the details of that cube word It's much more suited. I think we also get these questions about windows container all the time and I always recommend cube word because cube word. I think is yeah, it's a vm running in In your kubernetes cluster and you can run any windows version you you like and I think it's more capable for migrations scenarios at least Than windows containers because you can't can't pack anything in windows containers Yeah, one of the things I've really wondered about windows containers is where people getting images from right As obviously you can't use a linux container image to create a windows container No, we talk different ones. Sure You have to build some on yo Yeah Does code ready workspaces work on okd or is there an upstream operator version? Uh, yes, it's uh eclipse che that there is and there is an operator. Um for for eclipse che cool So yeah, it's not exactly code ready workspaces, but it's the upstream of code ready workspaces eclipse che. Yeah yeah Yeah, we also have support for uh, okd based, uh, code ready containers like single node development versions of of okd awesome Did we get all the questions? Yeah Looking back. Let's see It's not um one one of the things I want to say is as as someone who's been Playing with since the early days of origin in okd. I am really grateful to all the folks who are on this call And all the other folks in the okd working group That are community members who have come and given their feedback over the years and really encourage everybody Since it's open source. We don't know that you're out there. It's not dated We have no clue who you are So if you raise up your hand and and and join the okd working group, um, we'd love to have you there Um and ask your questions again in the kubernetes slack. Um in openshift dash dev And this has been one of the most wonderful and rewarding groups of people to work with over the past few years it's really grown exponentially um and you know The feedback we've gotten and the testing and the deployment Marathon we did a year ago and then another okd Testing and deployment workshop. We're all community driven. If you go to open shifts YouTube channel, which is I think youtube.com Open shift all right open shift. There's a whole playlist of videos of people walking through deployments for okd And they're really great and the guides are a great supplement to those and we really are looking for You know, I keep saying it other permutations of how you want to deploy okd and that and Just stretching the edges of where Open shift lives and breeze out there. So please do join us. Um, we're really One of the most receptive and effective groups of folks and there's no Silly questions only silly walks Um Never walk alone walk with the arc you do okd working group nice Later a minister yet though for the silly walks Okay So that could be you new contributor roles available. Yeah I can anyone else have any other closing thoughts for this session Let's officer session Just wanted to say thanks for having us on here. Thanks chris Thanks josh, and this has been um, it's always great to be able to tell people what we're working on and to bring more people into the fold So very much appreciated Well, thank you for coming on we really thanks everybody and thanks for all the questions Um, hopefully we answered them for you and if not you can follow up in the community Bye everybody. Thank you very much. Take care all Bye