 Let's say I will assign the cost 10. Now the template is ready. And we need to set up quotas. So we have another CR, cost of template quota. I already have one where I'm allowing two instances of the DEF CONF cluster and the budget for this name space is 25. And I want to add another one. So I will allow just one instance of the demo template that we just created. So this is where the admin flow ends. And everything is ready for the users to use our template and so they can provision their new clusters. So now I can log in as a user on this cluster. And I think I'm already logged in. So let's check. OK, yeah. So that's my username user. And this user has very limited permissions on the cluster. So if I try to do OC getBot, I will be rejected if the internet will start working. OK, finally. So you can see I cannot get bots. But I have one project within which I can operate. And that's the debuser namespace. And the only things that I can do is that I can explore what cluster templates are on the cluster. So we have these three templates. The demo template is the new one that we just created. And every template has a cost. I can explore what kind of quota is in my namespace. I can take a closer look. So I can see that as a user, I can create two instances of this DevCon cluster and one instance of the demo template. And in the status, I see that I already spent 10 budget, right? And I have 25 maximum. And then what kind of clusters I already have. So I have one DevCon cluster and zero of the demo template. So let's try to create a cluster from the demo template. I need to create a cluster template instance. So I already have a cluster template break out. So every cluster template instance, in the spec, we have a cluster template reference. So this should reference the template that we want to use. So I need to change this to demo template. And then I can provide the parameters for the template, right? Because the admin allowed me to use whichever version I want. So I will use the 411.12. So let me change the template. It's called demo template. And let me apply it. All right, so the request to create a cluster template instance was successful. I can again check the quotas. And I can see that in the status, I have a new demo template and the count is 1, right? And the budget spent is 20 because the cost of the cluster template was 10. So if I would try to create another one, I won't be allowed to do it. Because there is a webhook, which is checking whether we are within the quota that was specified. So the cluster provisioning is running. We can check that. So in the cluster template instance that we created in the status, we will see how the provisioning is going. So we have conditions here, which are basically showing all the progress of the cluster deployment. So the first condition that we have here is the cluster definition created, which is true. So that means that we created the application and the Argo CD is taking care of the HelmChart deployment. Then it shows whether the cluster installation was successful. That's true. So it already created a cluster because it's a hypershift cluster, so it was very fast. Yeah, and then when we create this cluster, we add the cluster to Argo so Argo can manage that cluster. So that was already done. And then Argo will apply the cluster setup, so it will start creating the Kafka on the new cluster. And after all is done, I will get the access to my cluster. So there is admin password and also the URL of the API. So I can grab my password, this one. And I can take my API URL, I can log in. OK, so now I'm logged in to my new cluster. Let's try whether the Kafka that I wanted to have deployed on that cluster is running. So they just grabbed these commands from the example of the Kafka cluster. So I will run a Kafka consumer here and in the another terminal, Kafka producer. And once that is running, I will be able to type something into the Kafka producer, so full. And it should appear in the Kafka consumer. OK, so that's it. Do you have any questions? Oc get notes on what? On that window, I need to write. Oh, sure. Yeah, so the question was whether I can show the notes on the newly provisioned cluster. OK. So and another question. Can you please celebrate a little bit about that agent platform within hypershift config? Sorry, can you repeat? So you have a CR for hypershift, and you have a platform agent there. So could you elaborate a little bit what this is? Oh, yeah, sure. So how agent platform works is that you will create an infrastructure environment, which is the CR, and that infrastructure environment will provide you with the ISO. You take that ISO, and you boot up your bare metal machine, or VM machine, or whatever, and you boot it up, and it will appear as an agent inside that infrastructure environment. So I already did that, because I didn't want to spend time on that. So you have an agent in that infrastructure environment. And when we take a look at the Helm chart that we created in the Notebook, it says that in the hosted cluster, it says that the infrastructure environment that I want to use is called DevConf Infra. So I'm picking agents from that DevConf Infra. And in the Notebook, I can say what kind of agents I want. So you can specify. You can pick them by the label. And I just said that it can just pick any agent from that infrastructure environment. OK, any other question? Maybe we'll show that later. But what is this project? Is it bundled with something, or is it a standalone operator? Where can we find more info about that? How can we install it? OK, so this project is very new. We don't even have a first release yet, but we are working on that. So hopefully next week, we will have something. But currently, it's a standalone operator. It should be available on the operator app soon. And maybe later, it will be part of that MCE project. That's why I started with it. Because at the time when I was writing this presentation, we wanted to include it in the next release of the MCE, but then it was decided that we will postpone that. So it will be from the beginning, it will be a standalone operator available on the GitHub, but later it will be part of the MCE, probably. And where you can find it is, so on my last slide, there is a repository which you can check out. And right now, you can just build it yourself and run it, or just wait a week or so, and it will be on the operator app. And about the Ergo CD, you install it as a dependency, or you expect it's already installed on cluster? Yeah, it needs to be installed by you. And the same way for HyperShift, right? Yes, so you can either install MCE, which will bring the Hive and HyperShift, or you can just install those separately if you don't want the whole MCE package. Thank you. Okay, so that's all I have. Is there any other question? Yeah, another question about underlying infrastructure for provisioned cluster. So is there any cloud integration, like managing load balancers, service wire services, and that kind of stuff? Or it works just like a bare metal, and you need to figure out it yourself. I mean, you can deploy your cluster on AWS or GCP, or on anything that the Hive or HyperShift is using, because that's what we use to deploy the clusters. Yeah, so... So that basically depends on underlying HyperShift capability. Exactly, yeah. Okay, thanks. Is there any other question? Okay, cool. So thank you. Questions? Thank you. Thank you for asking us a lot.