 Hello! Do you want to learn how to deploy your CodeRoachDB cluster on Kubernetes and OpenShift? Then, this video is for you. My name is Alex Soto, Director of Developer Experience at Red Hat. And if you want to stay updated with all the content that we are delivering, remember to follow me on Twitter and subscribe to the channel. Okay, let's start here. I've got my OpenShift cluster running. Remember that OpenShift is just an implementation of Kubernetes. So, OpenShift is Kubernetes. Let's go to the terminal. I can do, for example, keepCuttleGetNode. So, you can see that, you know, I've got all these my nodes. I've got like six worker nodes and three master nodes running on AWS in front form. And now, let's deploy a cluster. Do I do keepCuttleGetPot? Do you see that keepCuttleGetPot? Do you see that I've got no POT deployed here yet? Let's deploy a CodeRoachDB cluster. The only thing that I need to do is just use Helm. So, I can do Helm repo at stable. And I put it, this, the KubernetesChart.storage.boggleAPI.com. I added the repo. Okay, then I need to, usually I just do a Helm repo update to just update to the last things. Probably now it's already the last one, but it's always nice to have it updated. And then I need to create some YAML file with the specific parameters of my installation. So I'm going, for example, to create a BI Cook RoachDB.yaml. Since I'm using Helm, most of the parameters are okay. But if I want to set it somewhere of all, I need to create a specific YAML file. In this case, notice that I'm just setting the limits and the records of the memory. So I just want to use one GWT RAM. The cache is a quarter of the old memory, so it's 256. And then my service, the service that is exposing Cook RoachDB, I wanted to not be a cluster IP, but a load balancer. Then I can just save the file and do Helm install. Let's call it, for example, Quarkus release, because at the end, someday we will deploy a Quarkus application, right? As we've seen in the previous video, in the description you can find it, the link where we develop a Quarkus application using Cook RoachDB as a database. So here we're just learning how to deploy it to Kubernetes, and you can take that application and deploy it here. So we've got, again, Helm install Quarkus release, minus, minus, minus values. It's going to, we call it Cook RoachDB.yaml and we want to use the stable slash Cook RoachDB. Okay, now I install it. It might take some time, but at the end, you know, now it works and I can do Cook RoachDB.getPort. And you can see that now my Cook RoachDB cluster is starting with three nodes by default, so you can set it more nodes if you wish in your, in your.yaml file, but in this case, I just leveraged to the forward stream. Notice that the init has completed so that my cluster is initialized. It's still, you know, waiting. Notice that now the node zero is running but not ready yet. The reason is that because not all the cluster is up and running. Let's wait a bit more. Okay, now notice that this is up and running and the other ones are running. They are waiting for the synchronization. Meanwhile, I can do Cook RoachDB.getServices. And you can see that here I've got two services, one which is the cluster AP and another one which is the Quarkus release co-group public, which is the load balancer. Remember that I said it to be a load balancer and this is the URL to connect. And in case of your application, you always need to do it through the public service. It doesn't matter if it's a load balancer or cluster AP or whatever, but always the service should be the Minus public one, not this one. This one is used for internal communications. And if you check the Cook RoachDB documentation, it says that you need to always use this service. Okay, the public one. Let's see if I've got all the pods up and running yet. Now, okay, I can just go here, copy the URL. Go to the IDE and maybe sometimes with Amazon it takes some time to publish, but I think that now it works. You can see that now I've connected to the Cook RoachDB dashboard and notice that, as I said, we've got three nodes. And here you can see also the hostname or the node name with all the memory, all the versions and so on and so forth. So really easy to deploy Cook RoachDB cluster inside a Kubernetes cluster. Remember that in the description, you've got the link on how to develop a Quarkus application using Cook RoachDB as a database. Now you've learned how to deploy the Cook RoachDB in Kubernetes. And in the next video, you're going to learn how to use Cook RoachDB in a multi-cluster environment. Thank you very much.