 Hello, hello, KubeCon. So I want to talk to you today about how to find some clarity in this cloudy landscape. So we've been on the stage, Cisco's been on the stage a few times, and we've introduced in the past kind of what's become this suite of open source projects. So we call it open clarity. And in the past, we've done... So what is open clarity? It's security, it's observability, both for your running Kubernetes clusters, for your APIs interacting between all of your applications, and openclarity.io. First up, API clarity. Second up, Kube clarity. What are these things? API clarity is a cloud-native visibility tool for APIs. We use service meshes. The goal is to analyze API traffic, capture your risks, and mitigate them. Now, for Kube clarity, Kube clarity is a tool for detection and management of software bills and mills of material. S-bombs, everyone needs an S-bomb. You need multiple S-bombs. If you want S-bombs, you can get some S-bombs with Kube clarity. So in your running Kubernetes clusters, you can run Kube clarity in your CICD pipelines and kind of get a better idea of what's happening in those clusters and mitigate some of those risks. Now, what if I told you that there was a secret third thing? We love clarity. We love an opportunity to create a logo with a cute animal. So introducing this week, function clarity. We thought about some of the different areas that you need to approach with one, getting clarity around your running code, as well as understanding some of the risks within your environments. So function clarity is meant as a framework for signing and validating cloud functions, right? So artifacts code, image code that you're running, lambda functions, what have you, different cloud providers. We got that. It's in the box, right? It's code integrity tool for serverless functions. Leveraging, I'm sure you've heard talk about SigStore, Cosign, Recore, FullCO, built on top of the, built on top of the SigStore policy controller. So that's gonna allow users to sign their functions, validate them in cloud environments, and overall just bring some clarity to something that is a little bit more, not as much focus is spent on serverless environments and the security of those environments. So that's what function clarity is here to do. I encourage you to check out the GitHub repo. Go to openclarity.io. And for function clarity, it's openclarity slash function clarity on GitHub. Now, reintroducing the open clarity umbrella. We've got API clarity, cube clarity, function clarity. And if you want to learn more about each of these components, one, check out the Cisco microsite. That's etni.cisco.com slash events slash kubecon 2.2. We are at booth D3. If you have not had an opportunity to get a screen printed hoodie, you should check that out. And there's going to be an upcoming session for function clarity. It's called code integrity in serverless functions. That's now or schmoole happening at 1045. So come hang out with us, play some games, watch some talks at our booth. And yeah, I will see you later. Thank you.