 here. My name is Christian Glombeck. I'm based out of Berlin, and I'm the RATED internal engineering chair on the OKD working group. So what am I going to present on today? What is OKD for? What is Fedora CoroS? A little preview demo of OKD for. A little bit about the road ahead. I'll plug the OKD working group. And also, I'll give you some things so you can try out the OKD for preview. All right, let's get started. What is OKD for? So OKD is the origin community distribution of Kubernetes. It's essentially the OpenShift code base plus Fedora CoroS. Fedora CoroS being the base operating system OpenShift or OKD runs on. And there's a little star right there. It could be any operating system based on RPM OS tree and ignition. So you may not know these technologies. RPM OS tree is a hybrid image and packaging system. It combines lip OS tree, which you may know from flat packs, and a lip DNF, which is the package system we use in Fedora land and now also in REL8. So, yeah, OKD for is obviously the successor to OKD 3.x, which is formerly also called Origin. So with OKD for we really trying to bring all of that new good stuff with the operators and the automatically updating cluster to the community, meaning while you need a subscription for OCP, we really want to commit to always having a free and open source and freely available version of everything in REL8. So with OKD for we want to deliver on that promise. And I know we're a bit late with getting there, but yeah. Finally, today we got the alpha out, so very happy about that. Yeah, I want to shout out to Vadim Rukovsky and Clayton Coleman, who have done lots of work making this a thing, making this a reality. So, yeah, great work. All right, next on the agenda, what is Fedora-CoroS? So we replaced, in OCP it runs on RATAT-CoroS, which is in, it's not a standalone product, it's an implementation detail of OCP. Now in OKD, we replaced that with Fedora-CoroS, and we're actually not settled on, it has to be Fedora-CoroS and we're open to working on getting more operating systems supported as base OSes. Right now in the alpha, we chose Fedora-CoroS because it was the path of least resistance for us. So what is Fedora-CoroS? It's an automatically updating Linux OS. So yeah, we have automatic updates enabled by default, I think, in the standard Fedora-CoroS. In the OKD use case, we use a slightly different updating mechanism. But yeah, in general, it's a OS aimed at containerized workloads. It's based on RPM OS tree and ignition. Ignition, you might, I think, skip that. Ignition is the first boot provisioning and configuration tool we use and that came in with the CoroS acquisition, which is a really cool thing. We can really declaratively configure machines in different clouds on first boot. So really cool. Fedora-CoroS, as the name says, is composed of Fedora-RPM packages. It doesn't use the same build system for creating the images. We have the CoroS assembler for that, which you can use to actually build your own OS out of RPM packages. Yeah, Fedora-CoroS is also called F-Cos. That's the thing that, you know, we developers at Red Hat like to use. And yeah, we chose it as the base OS for OKD on F-Cos, which is the alpha right now. Yeah, a little plug. The CoroS assembler, if you want to try to build your own OS, it's not too hard to do it with it. It's a really cool thing. Try it out. Next thing, the OKD preview, OKD for preview demo. Let's hope it all works and I have internet access. So I opened up, I just spun this up before, the spinning up finished like five minutes before my talk. So right on time. As you can see, this has the OKD logo. It's the web console. And I'm not going to go too much into detail here, but I'm not sure if you can see that. Just to prove, this cluster runs on Fedora-CoroS preview. So Fedora-CoroS itself is still in preview stage, but it works already as base for OKD. Yeah, I could demo more, but I'm not going to go into that. It takes ages to load pages. So back to the presentation. All right, the road ahead. We have in the OKD working group agreed on a road map for version four. And that road map was three phases, phase zero, which was sort of the internal preparation to get the alpha out. And we've done that. Phase zero ends today. So we're starting with phase one now, which is actually getting towards a general, yeah, a GA release with a bit more stability. That's going to be phase one, you know, building stuff a little bit more out a little bit more of the CI and doing things a little bit more how we want them to see in the long run. And then in phase two, we want to look at bringing in more community collaboration and using that also for technology incubation. So if you have something you want to see in OCP one day, maybe the OKD working group would be the right place to actually start, you know, pitching that so we can try to get it in the code base. So yeah, the OKD working group. If you want to join or have a look, it's on GitHub in the OpenShift organization, the community repo. We are on Slack on the OpenShift dev channel on the Kubernetes Slack and also on the OpenShift common Slack in the general channel. There is bi-weekly video conference meetings with Diane Mueller, Danny Kumnia, or what is it, the community engineering chair and myself. And we also have a Google group, which we use as a mailing list for announcements and all that. So you're welcome to come by and say hello and contribute, of course. Yeah, and the most interesting thing I think today is we got the alpha release out and everybody is welcome to try it. Go to OKD.io slash download.html and you'll find instructions there on how to spin up your own OKD cluster. The repo, I think currently there's only the readme in there, is OpenShift slash OKD on GitHub. And if you want to have a look about the releases we're building continuously, then go to this origin dash release.svc.ci.openshift.arc webpage where you'll see all the other builds. Yeah, that's it real quick for me. I hope if you're interested, drop by. We'll have office hours tomorrow where you can just come. It's in the Marriott gas lamp, in the gas lamp meeting room on the 8th floor, tomorrow from 11 to 1. I'm not sure if I have time to take any questions. Hold the questions until the AMA session, but also if you come tomorrow where we have a two hour session as you said at the gas lamp Marriott, which is right across from the convention center on the 8th floor, and we'll be there and we can answer any questions and we can try some of this. So this was an early wonderful birthday present. So thank you, Christian, and thank you, everybody.