 Hello, my name is Jose Severo, and I'm a technical marketing manager here at GitLab. In this short video, I'm going to cover a feature introduced in 14.0 called cluster management project template. In this release, we're moving away from the CICD template-based approach for cluster management. Instead, we're using this template. And the benefit for this new approach is that you have total control of your applications that are deployed through this cluster management project template. You can customize them any way you want. Additionally, the new applications will be installed using Helm version 3. And in this release, the cluster management project supports only a certificate-based cluster integrations. But we plan to add support for a GitLab Kubernetes agent in the next release. So let's go to showing this new feature. So here I'm inside a group called Tech Marketing. So I'm going to go ahead and create a new group. And we can call it GitLab 14.0. You can make it public or private, it's up to you. And let's go ahead and create a Kubernetes cluster of the group level and then using this new way of rolling out applications to it. So first, we need to create the Kubernetes cluster. So let's click on Kubernetes. We're going to choose Amazon EKS. And we can choose US East 2.0. We'll call it C-708KsCluster2. After a few minutes, this message will switch to a message in green that says cluster was successfully created. So now your EKS cluster is up and running. And notice now that in here, there is no longer a tab for applications. And there's actually a warning message here saying warning you that one click application management was removed. So GitLab 14.0. Let's move on to the next step, which is actually how do we deploy Ingress, CertManager, for example, and other applications. So for that, we need to go to the group and let's create a project here. And let's click on create from template. And let's look for GitLab cluster management project here. So let's use the template. Let's call it cluster management. We can make it private or public. I'm going to make it public here. Okay, now that the project has been created, you see some files here. So what you need to do next is go to the open the helm file YAML. And this is what's included in the default template. There's a bunch of applications here. The ones we want to uncomment are Ingress, CertManager, and Prometheus for monitoring. Remember, when we can make a commit here, this pipeline will be automatically launched. But before we make this change, we need to go back to your Kubernetes. Let's go back up to the group and to the cluster. And we go to advanced settings and here where it says cluster management project. You need to select the project that we just created to do the cluster management. And here, as the note says, this project can be used to run deployment jobs with Kubernetes cluster admin privileges. So we save the changes. Now we go back to the cluster management project. Go to helm file YAML. Now let's edit this file and uncomment Ingress, CertManager to handle all the certificates with secure communications and Prometheus for monitoring. And we need the Ingress to be able to access our EKS cluster from the internet. So as soon as we commit changes, we go to CICD pipelines. There is this pipeline running. And this is the pipeline that is actually deploying the applications to the EKS cluster now. After a couple of minutes, you will see that the pipeline completes. All the jobs are here green. So that means that the applications now have been deployed to the EKS cluster. That means the CertManager, Ingress and Prometheus are up and running. Now, in order to complete the configuration of the EKS cluster, we need to set the base domain. Now to be able to set the base domain, we need the IP address of the Ingress that is up and running. So how do we get that? Let's go through the steps. So first, I want to paste a command here. So this command will add an entry to my local kube config so that I can then issue kube control commands from my command line. So I have a previous run here right above it. So what I'm going to do first is I'm going to copy. You can get your own ARN from your AWS account. So we're going to paste that. And then I got to put my cluster name here. And the rest is correct. And then press return. All right. So that has been added now to my local kube config. So now I can issue kube control commands. Let me execute it one more time. So let's paste this other command. There you go. So this command will return the value, the IP address of the Ingress. There you go. So let's break out of it now. Control C. I'm going to copy the external IP address. And then you need to add a CNAME type DNS entry that points to this external IP. So I have this domain called gitlabworkshops.com. So I've logged on to the, to IONOS is the one, the provider. So I've logged on to the interface. I've gone to the DNS UI and I'm going to go ahead and add a record. Okay. Good. So I'm going to add an DNS record and it's going to be CNAME. And then I'm going to call this wildcard.csavidra1. And it's going to point to the IP address returned by the kube control command that we just copied from the, from the command line here. And then I'm going to save. Good. So the CNAME record has been added to the DNS. And the last step is for the base domain. I need to say csavidra1 and is gitlabworkshops.com. And then you click on save and that's it. So we have finished setting up the EKS cluster and we have deployed applications to it. And now we can manage those applications from the cluster management project that we instantiated from a template. From now on we're going to customize if we need to the applications that we've deployed to Kubernetes from this project. So let's say if we want to change some parameters in Prometheus then we could do it here. You know, we can customize each of the applications at a more granular level. Very good. So I hope you enjoyed this short video and until next time. Thank you.