 I'm Christian Glombeck. I'm one of the co-chairs for the OKD Working Group. And yeah, we'll be presenting on the state of OKD4 today. So welcome, everybody. Let's have a look at the agenda first. So we'll go through what is OKD4, then what is Fedora Core OS. We'll have a OKD4 beta demo, then we'll have a quick look at the road ahead. Then an introduction to the OKD Working Group, and then just a call to try the OKD4 beta. Let's get started. What is OKD4? OKD4 is the origin community distribution of Kubernetes. It is the OpenShift code base that is also used for the OpenShift Compute platform, our product at Red Hat, also called OCP, plus Fedora Core OS. You can find all the info on OKD.io. So OKD4, a community distribution of Kubernetes plus plus, it's automated installation, patching, and updates from the OS app. What does that mean? So we actually have bundled the operating system with the cluster, and it's all packaged together. So from the lowest level to the application level, it's all automated operations. We have the Linux host with Fedora Core OS platform and cluster management, which is the OpenShift Kubernetes distribution. And then on top of that, we have operators that run the applications in an automated manner. So let's see what platforms we support. We run on bare metal VMs, OpenStack, AWS, Microsoft Azure, and Google Cloud Platforms. For some of those platforms, you may need to upload the images manually before you can start the installation process, which requires a little bit of manual work. But most of it is really driven by the installer and fully automated on most platforms as well. OK, going to the next section. What is Fedora Core OS? Fedora Core OS is an automatically updating Linux OS. It's aimed at containerized workloads. It's based on RPM OS tree and ignition. And it's built with Core OS assembler and composed of Fedora RPM packages. So let's pause here a little bit. That's a lot of information on one slide. We have taken the best learnings from the atomic host OS and from Core OS, which is the technology's RPM OS tree and ignition, and put them together in Fedora Core OS, and also in Red Hat Core OS, which replaces Fedora Core OS in OCP. In OCP, we have Red Hat Core OS, or Red Hat Enterprise Linux Core OS instead of Fedora Core OS, which is the main difference between OKD and OCP. They're built with a tool called Core OS assembler. You can actually build your own operating system out of RPMs with that. And ignition is used to do the first boot configuration here. So I really like the concept. It's super easy to provide the configuration upfront, and then ignition takes care of configuring everything on first boot. And RPM OS tree is our immutable host OS, or the system that builds immutable host images. So it's an image-based operating system. All right. I'll hand this off to Vadim now for the OKD4 beta demo. So Vadim, take it away. Hello. My name is Vadim Murkowski, and I will demo OKD4 today. So if you're familiar with OpenShift Container Platform, our web console, you will notice that OKD4 landing page, overview page, is very similar to OCP, except we use different branding. It will come to down. We use different branding for OKD. And other than that, we support all the features which OKD has, meaning monitoring, inventory, cluster inventory, and details pages and all like that. The most major difference is that we use Fedora Core OS as a basis for all our nodes. Thus, we use a newer kernel version and the newer packages, including Cryer on Time and so on. In OKD4, we also support community operators using Operator Hub. So users won't have to require a subscription from Red Hat to install operators. In fact, in order to install OKD4, they don't require any full secret at all. And OKD4 also has a developer view, same as OCP, where developers get away from complexity of bots, deployments, and so on, and work with a simplified version and better focus on deploying the code instead of working with Kubernetes Previews. We also talked a lot about operators. So OKD4 contains approximately 30 operators right now, which make it run. And in order to demonstrate their value, we have created a small game, which is similar to standard duck hunt. But every time I shoot the duck, we're killing a pod or removing a deployment. Yeah, that's enough. And we can see that those pods, and if I kill, but our cluster doesn't go down, because the operators are ensuring that all the necessary pods are being restarted and we create the wrong scratch if necessary. So the game shows the value of the operators. And that's pretty much all I've got. All right, thank you very much Vadim. Let's continue with your road ahead. So we have a roadmap for OKD4. And with the beta release, we're really in the middle of phase one, which is we have something that works and we're still stabilizing it. And phase two would be reached when we have a GA release ready, which is soon, hopefully. And we'll be focusing on community collaboration and technology incubation in phase two and in the future. So what we really want to do is invite the community to participate in an OpenShift development and have a feedback circle that we, as Reted, also get value from and that we fix issues on the newer Fedora CoreOS system, newer with the meaning of it has the newest kernel and things like C Groups V2 and everything that hasn't landed in Reted CoreOS, Reted Enterprise Linux CoreOS yet. So we really want to use OKD as a vehicle to stabilize things before they land in our product and also give the community the opportunity to use these things early on. So technology incubation is a huge part in collaboration with the community. There's also great projects like the OpenShift ACME controller that can be used to provision certificates for services and routes that run in OpenShift. And we want to put these kinds of things in OKD or make them optionally installable in OKD so the community really gets value out of this. So yeah, this is the road ahead. Let's go to the OKD working group. The OKD working group is the place where we meet and discuss openly the development and future plans for OKD. We have a Slack channel, OpenShift Dev on the kubernetes.slack.com. We also have an OpenShift Commons Slack where you can find us in the general channel and also in the OKD for channel. We have a Google group, which you can find under that link. That's also used as our mailing list, so you can subscribe to that group and you'll get invitations to the bi-weekly video conference meetings, for example, which you can also, which we hold and you can find a calendar where those are marked on the Fedora, FedoCal under the link below. We also have two repositories. One is the github.com OpenShift slash community repository, which we use to track things we want to discuss in the meetings. And we have the OpenShift slash OKD repository, which is our tracker for our bug tracker, essentially. So with that, I would like to call on everybody to try the OKD for beta. You can find it on OKD.io slash download.html. And there's a few more resources linked here. The docs.okd.io, then we have our release viewer where you can see all the builds from our CI system and even try out newer unreleased versions. And again, those two repositories. So with that, I would like to say thank you for listening in and I hope you're enjoying working with OKD.