 The GitLab Kubernetes agent allows a secure bi-directional connection between GitLab and any Kubernetes cluster. In this video, I'll show you how to set up this connection using the newly introduced GitLab Kubernetes agent user interface, which streamlines the setup of your GitOps workflows. Hi, my name is Cesar Saavedra, Technical Marketing Manager at GitLab. Let's get started. We already have a Kubernetes cluster running. Since it's running at the group level, the app group level, let's go ahead and create a project inside this group. Within this directory, we'll create next a file called config.yaml, but it needs to be located under specific directory. The directory needs to be .gitlab. Agent Cesar Saavedra agent K. It is under agents where the configuration of all your agents will reside. In this case, I only have one agent. That directory will create a file called config.yaml. This is basically the configuration of the agent. This is saying that the project that will be observed for changes and updates is this one here, Tech Marketing City Workshop GitOps Apps pull-based GitOps, and the path under that project will be manifest and any file under that sub-directory that has the suffix yaml, yml, or json. Next, we need to go to the Kubernetes cluster. And on this screen, you see the Kubernetes cluster there, SNEKS cluster, and we click on GitLab Agent Managed Clusters. We say integrate with GitLab, and here we select the agent that we just created. Now to install the agent that runs within the Kubernetes cluster, here's the command we need to run. So let's copy the command. Here I have set up my command line to be able to connect to the EKS cluster, and I've done that by creating a file called config, Cesar Saavedra GitOps EKS under my .cubed directory, and this is basically the information that I need to provide to the cube config so that it can successfully log in or connect to the cluster. And that's the HTTP address for it. One more thing I did was I defined a variable called cube config that points to that specific file. That way, when I run this command, it should be connecting to it. Very good. So the GitLab agent has been installed on the Kubernetes cluster. Let's check the pods that are up and running, and there it is. The agent is deployed and running in the EKS cluster. So let's head to the pool-based directory. And in here, let's go ahead and create a folder called manifest. And in manifest, let's create a file that we'll call nginx.yaml. Let's paste the configuration for an nginx deployment. There are now two nginx pods up and running. And as you can see here, there were two replicas, so that's consistent. So let's add one more. So let's edit. Let's put a three here. And before we do that, let me see if we can do the following. Let's do a watch here. Very good. So let's commit changes and see if there's a third nginx deployment that is spawned. And there it is. The Kubernetes agent is actually taking care of bringing up a third nginx instance. As soon as the yaml file was updated. So that's one and two. And it's creating one right there. And there it is. The three nginx pods up and running. So we have shown how you can streamline the integration of your Kubernetes clusters for use in your GitOps workflows by using the new GitLab Kubernetes agent user interface. I hope you enjoyed the video and until next time.