 So, real quick today, I love that Matt touched on security so much in this intro. That's a spot that's near and dear to my heart. One of the areas that I work a lot is with NIST, standardizing security around microservices. And one of the big things that we've honed in on is Envoy as this engine for a cloud native security kernel. So I want to touch on that real quick, why we think this is important and why we're excited about some of the work in the project that's happening around it. So like I said, I write standards around zero trust and I hate the phrase zero trust. It's an awful phrase. It's not well understood, but in short, you know, the attacker is already in the network and therefore our job is to bound attacks in space and in time because traditional perimeter security doesn't really do that for us. And Envoy enables us to do this, whether we use it in the mesh as a sidecar or whether we use it at Ingress for traffic that's coming in, whether we use it as an egress proxy for things going out. Envoy is a phenomenal tool for helping bound attacks in space and time at the network level. Even more, what I work on with NIST is this idea of Envoy becoming a policy enforcement point for all sorts of policy, whether that's network oriented, you know, service-to-service or Z, whether that's custom business logic that happens in WebAssembly, whether that's API gateway style things that's happening as part of Envoy Gateway, for example. All of these pieces are policy that Envoy helps us implement. And so we want to see it go everywhere. We would like to see Envoy widely adopted because it gives us this common point to be able to implement all sorts of security and other policy. That's one of the reasons that we're so excited, and Matt mentioned some of the work on Envoy Gateway that's happening. That's why we're so excited about Envoy Gateway, which is a project that is really geared towards making it dead simple for developers to come in and use Envoy to get value, to actually get things done, not just, you know, handle bits and bytes on the network, but actually expose an API in a way that they can understand and get traffic to their applications, right? Like Matt said, honing in on some of these specific use cases where Envoy is really valuable, but hard to wrangle today. We're excited about this project because it's built on open and standard APIs like the Kubernetes Gateway API, and we'll look forward a little bit more as well. And it's got a really aggressive roadmap with a large community buy-in with real folks on the ground using it to replace, you know, heavyweight enterprise gateway software. And so that's driving a really compelling set of use cases, and we would love to see folks hop in and participate here especially. But in this vein of enabling Envoy everywhere, we want to see adoption. And we believe that one of the best ways that we can facilitate adoption for developers, not the folks that are in this room that, you know, know Envoy and work with it, but everybody else is abstraction above the APIs that we're used to working with. XDS is really low-level. Envoy has this perception of being a low-level project, right? So we want to start to bring that up. The gateway APIs are one set, and we want to go even further with things like open API spec. The goal being to get as close to the developers as we can with Envoy early in the development process so it becomes usable and valuable for everybody and not just for this platform team that's trying to do, you know, this heavy networking work. And exactly like I said, you know, we want to see it more widely adopted because we believe that this leads us to a world where we can have a more safe and secure infrastructure across the board. This is stuff I'm working on standardizing from the spec and government standard space, and this is something we have engineers on the ground working on with Envoy capabilities, features, and insecurity. And that's all. You know, we're really excited about Envoy Gateway. Please go look and for folks that are interested in that space, come in and dive in. And if you're interested in working on some of these things full-time, we're hiring as well. But thank you all.