 So today, I just want to talk about something basic right now, and I think we all use some kind of CI CD tool in our companies, right? So I'm going to talk about Jenkins library, keeping the pipelines dry. So the overview is like a typical enterprise runs like hundred and even thousands of pipelines. Like for the deployment, we have a lot of pipelines, right? If you guys are using Jenkins at your places, then. And we have a lot of steps which are common and for example, build, test, deploy steps are usually same. So such code is usually duplicated and we really don't like the same code to be everywhere, right? And making updates is also difficult. For example, if we are shifting from Helm to Kanka, which is recently released, it is just an example. And so we'll have to manually go and do changes in the pipelines, which doesn't make sense. Or we can usually keep, or we can simply keep one library and then we can import it in different pipelines and get our work done easily. So this is not a new concept, but yes, this is something which is provided by Jenkins, which make it useful. And I'll define the use cases where we can get the complicated stuff done by this. So for the reference, I did my GSoc project last year, like I graduated recently and it was around the Jenkins. And there I got introduced by Jenkins library and I was amazed. Okay, this do a lot of work. So it's like a rescue, you know? So it has access to all the JVM features. So this is something repeated, so I'll just skip this. So this is something which looks amazing because we've been talking about Kubernetes since morning. And so yeah, so let's talk about this. So I give a simple, you know, Helm Upgrade, the other example, that is like the simple example. So that is like we can have a common library and then we can import it in our Jenkins pipelines, where the deployment is done for the staging or the production, and then we can get it done. Simply like this, I think this is not much clear, but in Jenkins pipeline, we have different stages. For example, if you want to build the whole thing and so there will be a different stage for build and for deploy staging. So we can, if we just call deploy staging and that there's a Jenkins library to it, we can write a different groovy script, you know, in one of the repo and then we can just import it in our script, import it in our Jenkins pipeline and we can get that work done. So basically I'll just give you a simple example. For example, we work on our namespaces, right? Like in staging, different teams have different namespaces. And you want the code, you want the namespaces to be updated always. So for example, so this is what I recently worked on. And I'll talk about that. So there's a thing called grab, which basically you can even export, you can even use Kubernetes Client inside your Jenkins shared library. And, and trust me, Kubernetes Client can do a lot of work. So I'm going to give an example to this. Or you do, you do your kubectl get pods and kubectl get namespaces in your terminal, right? You can get that work done by Kubernetes Client. And so if you want to, you know, if you want your namespaces to be updated. So this is a simple case. For example, there's a branch which is merged, or there's a push which is done to any branch, to a master. So that is going to trigger a pipeline, right? And you can use Kubernetes Client in the back, where you can list out all the namespaces, where you can list out all the namespaces. And from annotations, you can get key with service and which branch, with service and which branch. Like list out all the namespaces which has that service and that branch, which has, which has been just merged. And then we can, we can deploy that pipeline, or we can deploy those namespaces to a pipeline which updates all the services. So that is how we're going to get the updated namespaces. So this is the simple case which I, which I, so, so basically this is a process of continuous deployment, right? So you can get it done by Jenkins shared library in which you can just put the whole thing together. So this was the simple thing and I already gave an example of Helm and Tonka. So this is like one of the thing which I liked about Jenkins library and which is a basic thing that, it's a very basic thing, but yes. It can do our work simply. So, yeah, thank you.