 Good afternoon everyone, my name is Keith McClellan, I'm the Director of Partner Solutions Engineering at Cockroach Labs. Clearly, I am not an AV specialist. I will be talking today a little bit about Cockroach DB and a little bit more about Cockroach DB on OpenShift. And I apologize if I'm completely thrown off by the technical difficulties. So, if I am terrible, it is all my fault and if I'm brilliant, I'm sure it is all to Mr. Waite's credit. What is Cockroach DB? Cockroach DB is a distributed SQL database. We bring together the best of the relational RDBMS world and the best of the SQL world in a database that allows you to run system of record workloads in a Kubernetes-native environment. That means a whole lot of things to a lot of people and I'd be happy to talk to all of you about that in more depth another time. But to start, we're a database that is architected to scale out rather than scale up. That means when you need more capacity, you add more nodes to your cluster. This is not too dissimilar to Kubernetes, which is so it's not probably too surprising to folks in this room that we run well in OpenShift because of that. And what we've done is we've presented a familiar SQL interface based on the Postgres wire protocol so your applications can connect to Cockroach DB just like they can connect to any Postgres database. Because we can scale our database by adding more nodes, whenever there is a capacity challenge in a database, whether you need to store more data or you need more transactions per second or you need to be able to host more users, you solve that problem rather than by buying larger and more expensive servers by just adding a few more instances of Cockroach DB to your environment. Because of the way we scale out, we're inherently distributed and that means that we can distribute across not only multiple nodes but multiple sites as well. And in OpenShift in Kubernetes land, that means we can distribute across multiple Kubernetes clusters, multiple OpenShift clusters and provision a single logical database to solve all of your computing challenges. Because of that, we're also inherently multi-cloud, which means you can have an OpenShift cluster running in AWS, you can have an OpenShift cluster running in GCP, you can have an OpenShift cluster running in Azure and have that be one database. Not three databases that you have to maintain and keep in sync, but one single database that all of your applications and users can interact with. So not only can we survive, say, a node failure or a Kubernetes cluster, an OpenShift cluster failure, we can survive the failure of an entire cloud provider if that were to become a problem for anybody. And we do that while guaranteeing no data loss and no disruption to your applications. So how do we do this? Not only do we present a database and not only did we build it from the ground up to work with Kubernetes, but we do that by providing an OpenShift certified Kubernetes operator for CockroachDB that gives you kind of our world-class, the information from our SREs and a world-class operator that will allow you to provision and manage your CockrochDB environment in OpenShift without requiring dedicated staff. Because of all of that stuff that we just talked about, running CockroachDB on OpenShift is a extremely easy experience, much easier than getting these slides up here today. So thank you all so much for your time. If you are interested in learning more, we do have a university where you can go and take some online classes and learn a little bit more about CockroachDB. And then you guys are going to be on the showroom floor. And we are going to be on the showroom floor. I will personally be on the showroom floor for the next three days. So please come and visit with me and we'd be happy to tell you more about the database and maybe even show it off a little bit. Are you guys donating $3 to some causal labor? We are in fact donating $3 to Women Who Code for anyone who attends either our virtual or in-person booth and lets us scan their batch. So thank you for that as well, Mr. Wake. Thank you.