 Okay, let's get started. Good morning, folks. Welcome to EnvoyCon, North America. So, I'm not Matt Klein. I am another Matt. My name is Matt Turner. I'm a software engineer at TechRate. I am the event chair for today. That doesn't mean too much. It basically means I stepped in to help out with all the admin. So I managed the CFP and put together today's schedule for you all, which I hope you really enjoy. Matt was actually going to drop by. He actually can't make it now. So I could give you a bunch of sort of Envoy statistics like lines of code and number of contributors and all stuff like that. But I'm sure Alyssa and the other folks are going to do an amazing job of giving you that overview and update. So I'll just sort of cover some housekeeping stuff this morning. I know Alyssa's been practicing her best Idaho accent. I think she even has a wig. Okay, so if you're super new to the Envoy project, you don't really know what it is. Again, the other folks will cover that, but it's super exciting. It's used by all the major service meshes, and it's used in a bunch of other places that you probably don't know about and might not realize, but we're hopefully going to learn about that today in addition to hearing for some end users and some developers on some new features and some new techniques. So for me, I'll just say welcome. I'm going to keep my just little speech fairly low key and I'll just go through some housekeeping. So we do have a code of conduct. We do take it seriously. You can follow that QR code if you want to read the small print of it. Please do not touch or hug people without their consent. Please do not misgender people. If you misgender somebody and you are corrected, just apologize. Use the correct pronouns and move on with your day. This hopefully isn't difficult, but we will be taking it seriously. There's going to be some captioning and some translations. You can scan that QR code and follow the instructions, put in a couple of details, and you'll get some captioning with some translation if that would help. We will be having, yeah, there's probably all of you have had coffee on the way in. There's going to be a morning refreshment break and afternoon refreshment break. There is a fairly long lunch break. And then the CNCF has a co-located events party, a bit of free beer this evening. I actually don't know where it is yet, but I'll find out before I close this out at 5 p.m. I think it's in this building somewhere. I know we haven't done this one yet, but the call for papers is open for KubeCon Paris, for the co-located events over there. It does take a while to get submissions in, to read them, to review them, to put a schedule together, to work with everybody. This pipeline takes a long time, so we are starting already. If anybody's interested in joining us in Paris, coming in and saying a few words, then you can start submitting already. And please evangelize this event in person. You know, everybody's around for the rest of the week meeting a bunch of people. If you could talk on social media, talk to folks in person. I know we've got a bunch of Envoy developers and maintainers here in the room, and that's great. But if you know more folks who work on the project or who consume it in really advanced ways and just don't tell anybody about it, then please let them know what a great time you had and that they should check out the sessions on YouTube and come along in Paris. I also try to put together a focus on the end users today. I know we've got some here, but probably not enough. Envoy is not just used in service meshes. I'm sure there's a lot of Envoy cloud providers. If you know of anybody, like I say, who does use it for other things, then please let them know about this event. Thanks to Google Clouds, who are our goal sponsor. This event wouldn't have gone ahead without them. And I've got a few Googlers speaking today. We're actually inundated with submissions, so everybody had to leave on the bench, like sorry. That's basically just a talk cap, but thanks for everybody's support all the way through the process. Thank you to the program committee members. I guess all of them are thankless tasks to read those submissions carefully and do all those reviews and give feedback, but the feedback was invaluable in putting the schedule together. And I don't think they're here, but thanks to the CNCF, who've actually helped with all the admin it is, especially Alessandra and Lindy. Okay, so I originally had a nice schedule with a bit of a narrative weave through it. There were some nice chunks of similar content. We moved from one topic to another for a few talks, but a few folks have had to drop out and there's been some schedule clashes, so there isn't honestly too much structure left. It's going to be a bit of a grab bag if we'll talk about this C++ class and then we'll talk about this end-user experience, but it'll keep everybody on your toes. We do have a list right first doing a general overview of the main proxy project, and then I think you're maybe going to double click on mobile right, which is sort of your particular favorite. There is one block left, like just after lunch, we're going to get three talks in a row on Envoy Gateway, so there's going to be a project update, there's going to be an end-user report, and there's going to be an awesome session on threat modeling and a security evaluation of Envoy Gateway and the Gateway API. Excuse me, I got a super ill on the flight yesterday. I may go home after this, but I wanted to say hi. We'll not share this mic, by the way, this is mine. Anybody who is speaking, we have the one lapel mic that you'll be wearing, please see the AV just before your session, in the break before your session to get miked up, have your laptop ready to go, you can block it in here. Time permitting in each session, if the speakers are up for it, we can take questions. The easiest way is to come and stand up to the question mic to make sure you can be heard and make sure you get on the recording, that's actually quite important, so I guess form an orderly line or raise your hand, but then please use that mic because it's not just about the speaker hearing you write, it's about the recording picking it up, and I think that's all the admin I have, so without further ado, I'm going to hand over to our first speaker. Thanks, everyone.