 Well thank you everybody for joining us today and good morning, good afternoon, and good evening wherever you are in the world. Welcome to the testing and deployment workshop. I'm going to give you a quick overview of OKD. We're going to start with an overview, talk a little bit about where we are current state of OKD, spend a little bit of time talking about operators and the operator hub, and then finally leave you with a whole bunch of links and references for how you can get in contact with us. So OKD, what is it? It is a community distribution of Kubernetes, but it's actually more than that. It's a community distribution of Kubernetes that is actually built off of the OpenShift code base. So it is the same code that you are running in your data center or on your cloud provider if you are a Red Hat OpenShift subscriber. This code base is what we build OKD from with very little, if any, variation. The only variation really is the fact that rather than running on the Red Hat Core OS, we're running on the upstream of Red Hat Core OS, which is the Fedora Core OS. So you've got the OpenShift code base with Fedora Core OS as the underlying operating system. And as Diane mentioned earlier, you can reach us at OKD.io to find documentation, reference materials, and code ready containers built from OKD, which I'll talk about here in just a minute. So like I said, this is a community distribution, means it is built and supported by a community, some of whom you're seeing on your screen right now. The whole premise behind OpenShift as sort of a Kubernetes plus distribution is that automation is king. Automation for installation, automation for patching and updates, and automation for resiliency and recovery in your data center or your cloud platform. Like any other Kubernetes distribution, its heart and soul is really the orchestration of applications and services that provide value for your business or your organization. Underlying that is base Kubernetes, the platform, the cluster management, the security, the monitoring, embedded registry, everything that you expect from a Kubernetes distribution with a twist of additional automation provided by the OpenShift plus plus. As I mentioned, Fedora Core OS is the underlying operating system on which the whole thing is built, and Fedora Core OS itself brings a lot of what provides the automation and the resiliency to OKD as a Kubernetes distribution. You can run this on just about any platform you can imagine. We're not quite to ARM64, but you can bet there are people who care about ARM64 and would love to see this thing running on the edge. Right now, all of the major cloud platforms, Amazon Web Services, Microsoft Azure, GCP, the Google Cloud Platform, you can run this on OpenStack, you can run it on Overt, and as some folks are going to demonstrate today, you can run it on VMware and bare metal. Let's talk a bit about where we are today. We've actually come quite a long ways since the major shift a couple of years ago from OKD 3.11 to the OpenShift 4 that OKD 4 is built on. We are currently in our 4.7 release with 4.8 not too far out on the horizon. We've been taking a lot of community contributions that are improving this platform and making it much richer as we continue to evolve. We've got active collaboration established now between both Fedora communities for our underlying operating system as well as folks who are contributing to the Operator Hub, which we'll talk a bit more about here in a couple of slides. There are quite a number of bespoke operators that are now available for OKD to provide all kinds of value add for your clusters. One of the things that this platform really allows you to do outside of like a subscription based OpenShift is enabling early adoption of upcoming technologies, especially with the underlying Fedora Core OS. You get a preview of what's coming down the road, which sometimes can bring an extra level of excitement, but always brings an extra level of functionality that you can take advantage of. We've also just recently, I was probably six months ago, I believe it was this summer, we got CodeReady Containers finally released for OKD4. CodeReady Containers for OKD is based on the CodeReady Containers code base for OpenShift. So just like everything else that we do with Red Hat, it's all open source. It all accepts community contributions. It enables you to run a single node OpenShift cluster on your laptop or workstation. So it gives you all the goodness that you get with an OKD4 cluster and Fedora Core OS on your local workstation. You just have to add your code. One quick note on that the CodeReady Containers release that is currently hanging off of our OKD.io site is still built on 4.6. If you're watching a recording of this video, it's very likely that the 4.7 release is out. So those of you who are watching us live look for the 4.7 of CodeReady Containers to be available here within the next week or two, hopefully within the next couple of days, but Dima and I are working on a couple of things that we got to get in place so that the build will run off of some fairly significant changes to the underlying Fedora Core OS and a couple of the operators that we need to update the code base to support CRC. So look for that to come very soon. Operators, operators are what make OKD run. In fact, the very first thing that happens when you're bootstrapping an OKD cluster is an operator is taking control to coordinate the rest of the installation. Operators provide infrastructure as code with intelligence behind them that monitors the state of the resources that the operator owns and is responsible for ensuring the stability, the resiliency, as well as the patching and updating. So operators are like a bundled system administrator that is always with you, always watching the application and ensuring that it continues to run. The core of OKD is built on operators. So everything that provides the functionality from etcdup is controlled by operators. But operators also bring value add. So if you need RookSef as a storage provisioner, well, there's an operator for that. Your internal image registry is an operator. If you need a Kafka cluster, there's a StrimZ operator. If you need a service mesh, well, there's an operator for that too. So operators are a way to bundle the capabilities that give your applications the added richness, resiliency and capability that you need so that as a provider of software solutions, all you have to focus on is your code and let the operator take care of everything else. The operator hub is where you can go to retrieve these and install them into your local cluster. When you have a cluster up and running, the operator hub will be there. From the console, you can navigate to the operator hub and go shopping. When you stand up an OKD for cluster, all of the operators that are available, you will be able to install free of charge. There are not subscription-based operators in there. They will be the community supported versions of the operators that you would see if you had a subscription-based OpenShift cluster. If you need Grafana or StrimZ or service mesh with Istio, they will all be there and installable from the operator hub. Now, another quick caveat on that. We are still working with several of the operator providers to ensure that the community version of the operator is available in operator hub. Some of them, you do still have to go to the GitHub repo wherever the operator lives to get the installation materials for it, but as we continue to evolve this ecosystem, more and more of those operators will be there. When you get your cluster up and running, you will see that there is already a very rich set of operators available. Finally, we would like to invite you to come join us. This is a community-driven ecosystem. We are very active, the OKD working group and the Fedora Core OS working group. We have several members actually that participate in both to a greater or lesser extent. You can find the OKD working group at the following links, which I will leave up on your screen for just a few seconds so you can screen grab or type down whatever you need to do to find us. We also have a calendar that will give you access to our bi-weekly meetings. They are open, so please come and join us. The same thing goes for the Fedora Core OS working group that is available at these links. Again, please come and join us if you're interested in edge networking, if you're interested in seeing ARM64 or if you're interested in seeing this run on other metal platforms, come and join us and contribute your knowledge, your skills and your time to our efforts. We are a community-led organization. The final thing I'll leave you with is a list of links where you can access our resources and come and talk to us. With that, I'll say thank you.