 In the first tech demo, whose link is included in the description of this video, we installed Flux and set it up to synchronize Kubernetes Manifests stored and managed by GitLab. In this tech demo, we covered the synchronization of Helm charts. We have already bootstrapped Flux into the project Flux-config. Heading over to the Flux-config repository and drilling into directory clusters, in my cluster, Flux-system, we see the Flux components and sync manifest that the bootstrap already created. And checking the pods of the cluster, we see the Flux-system-related pods up and running. The GitLab agent for Kubernetes provides secure connectivity between GitLab CICD pipelines and Kubernetes clusters. The agent has a Helm chart that can be used for deployment in Kubernetes clusters. As you can see, the agent has not yet been installed in the cluster. So let's have Flux do that by synchronizing the agent Helm chart with the cluster. The first thing we need to do is to create a configuration file for the GitLab agent for Kubernetes. This file needs to reside in the directory .gitlap slash agents, followed by a directory name of your choice. For example, k8s-agent, which is used as the name of the agent. This specific configuration is given access to the cluster from pipelines in any project that resides in group Flux GitOps. Let's proceed to register the agent. We select the k8s-agent agent from the drop down list and click on register. We copy the agent access token and save it. This token will be used as Flux deploys the agent to the cluster using its Helm controller. Notice that although we have registered the agent, it is still showing us never connected because it has not yet been deployed to the cluster. To have Flux do that, we head to my cluster directory and create a manifest called namespace-gitlap.yaml, which will create a new namespace called gitlap in the cluster. This update will be done via synchronization of this Kubernetes manifest by Flux. We cover this in the previous technical demo. We commit the changes and then watch the creation of new namespaces until we notice that Flux creates the gitlap namespace in the cluster. Next, let's create a secret yaml file for the token we saved earlier. We name this secret gitlap-agent-token-initial and then include the value of the token in a file called values.yaml. We run a kubectl apply using this manifest, which will result in the creation of the secret in the cluster. Let's head back to my cluster directory and create a manifest called agentk.yaml, which contains two Kubernetes resources in it. One is of kind helm repository and the second one is of kind helm release. The helm repository contains the metadata and specification of the source that contains the chart. In this case, it is charts.gitlap.io. Also the helm repository index will be fetched once an hour. This information is used by the source controller. The helm release contains the metadata and specification of the release of the helm chart. This information is used by the helm controller as a template to create a new helm chart resource in the same namespace as the source ref. The specification indicates that the chart name is gitlap-agent. The source ref points to the helm repository defined above and the reconciler will reconcile the release every hour. So one pod of the incluster agent will be deployed and this agent will communicate with gitlap via secure web sockets. Lastly, the previously created secret is provided to the helm release. As we watch the cluster pods, we see that Flex detects the helm chart updates to the repository and proceeds to instantiate the pod for the agent. The pod name starts with gitlap-agent and its namespace is gitlap. Now that the incluster agent is up and running, we see that the connection status of the KAS-agent is now connected. The combination of gitlap and flux can help you streamline your deployment processes to gain better collaboration among stakeholders in your organization, to lower your time to restore services or preempt on scheduled production outages, to innovate and deliver value to your customers faster, and to improve your compliance and always be audit ready. Thank you for watching and until next time.