 So I've been speaking for the last 18 months or so from my home on Zoom. So thank you, Michael, for the opportunity to come speak here and wear pants, because I haven't been wearing pants for a long time now. It's been an opportunity for me to really wear pants and speak. So just a quick way to sort of talk through what we do. So we are Jetstack, a company that sort of, you know, is behind the cert manager project for those who don't know or those who have been using cert manager for a long time. This is essentially a way for you to manage certificates within your OpenShift clusters, whether for your routes, whether for your ingresses, whether for your pods, whether for your mesh workloads, something that many of our customers have been using. Just as a little bit of a background, cert manager is an open source project, completely sort of, you know, being used by a large number of users, large number of organizations, many of you here in this room and also online probably use it. So something that we look forward for people to contribute also to extend and add more functionality. So Jetstack, like I said, is the company behind the cert manager project and over a period of, you know, the last couple of years we've added a lot of enterprise features that is very relevant to many of our OpenShift customers, especially many of our large banks that work very closely with us. And then today, I just want to sort of, you know, start with a little high level of, you know, what is that you get from cert manager? Basically a bunch of CRDs that allow you to create this certificate resource that automatically manages your certificate request with a CA that you configure, something that we refer to as an issuer. So you can have, you know, either a built-in issuer that comes in or an external issuer that you work with many other providers. The idea is that with this certificate request that manages the entire lifecycle, you have a way to manage X509 certificates and identities for all of the services and applications that are deployed in your cluster. That's essentially where sort of, you know, a lot of our organizations or a lot of the customers that we work with use it. But many of you know, there are a lot of places where certificates needs to be managed in Kubernetes. And in this session, which is a lightning round, I just wanted to sort of, you know, quickly take a little bit of time just talking mostly in the context of a service mesh. And the reason why I wanted to talk in the context of service mesh is, you know, majority of our OpenShift customers today are rolling out service mesh, either the Red Hat service mesh, which is a little, well, with Red Hat service mesh or also independently rolling out the service mesh directly from Istheop. Simple way, again, I don't want to bore you with this. You know what a service mesh is. There's a data plan, there's a proxy, there's data occurring across it. But the one important thing that we focus on is that catalog and ensuring that, you know, there is a mesh workload. Every mesh workload that you have is secured, is sort of, you know, identified with the SpiffySAN that is issued by and managed cert manager. So a simple idea being, you know, as you sort of, you know, grow, as you sort of, you know, manage your cluster. So there is a lot of need for ensuring, making sure that, you know, there is zero trust between every single component that is running within the cluster. Ingresses, securing ingress is one thing, but you know, also making sure that, you know, every single line of communication within your clusters are also secured. And basically you could say, all right, I got Istheop, got service mesh, it's got its built-in CA. Why do I need anything else? Because I get everything else, everything automatically with a service mesh because security is one of the three important things that a service mesh does. Fair question. One of the things that many of the enterprises that we work with wanna make sure is that the identity that is issued to the mesh workloads has its chain of trust established back to the CA that the organizations manage, the PKI teams manage, the InfoSex manage, because it's essentially the entire chain of trust that needs to be managed by the PKI team. So we have this project called Istheo CSR, the cert manager also has add-ons. Istheo CSR is one of the open source project again, basically built with the idea of making sure that all of your Istheo workloads and control plan components are secured using cert manager. Cert manager issuers that I talked about will sign and will deliver, will renew certificates, facilitating MGL as across the cluster. One of the, this is the important thing when I said that, why do I need anything else when I have Istheo? So cert manager essentially disables the Istheo at CA server and allows you to use cert manager with your CA, with the organization's PKI infrastructure that is in place to issue certificates and manage it. Automatic renewal obviously is built into cert manager and you get the benefit of automatically managing everything. And every time application is destroyed, kilpots, the private key material and all of the associated information about the secrets and everything is just gone. So that way, every time a new workload is deployed, you get new certificates that ties back to the organization's CA. So just secure is the enterprise offering that ties it all together. So like I mentioned, a lot of big organizations, especially enterprises, in addition to wanting cert manager support, enterprise support also work with us to manage their entire ecosystem of tools that they use within their OpenShift environments. Summary, just as a way to know Michael is looking at me and I'm gonna either run away from him with the mic and keep speaking or I'll have to give the mic back to him. One of those things will happen. But just as a way, we want your help, get engaged with us. We are on the Kubernetes Slack channel as cert manager, cert manager dev. There's a lot of people that sort of actively contribute. CS at Booth S52, that's where we are. We also have an after party, comes CS at the Booth and will tell you where, when, how, get drink with us. So looking forward to meeting with you all. Thank you so much. Thanks Michael.