 All right. Well, we made it. Thanks. I'm sure there's a service mesh joke in there somewhere first of all a giant Thank you to Craig for that extremely Musical introduction. I never thought I would see that but now I'm glad I think that I have so my name is William Morgan I'm one of the creators of linker D. I'm CEO of a company called buoyant I've been told that I'm a very boring person So I'm gonna give you a very boring update on a very boring project called linker D But first I'm gonna start with the exciting stuff So over the past 12 months, it's been really kind of a remarkable period for the linker D project our adoption grew by over double in in Europe and overall across the world since 2021 if you were virtually attending kubcon last year of the linker D team key noted on all the ways that linker D Has been used to combat the global COVID-19 pandemic. I'm very proud of that. We added fuss testing to the project We shipped exciting features like authorization policy and cross cluster failover And linker D. Of course became the very first CNCF graduated service mesh So very proud of all those accomplishments on on behalf of the entire community And of course, we've got some great adopters who joined our Ranks including Microsoft Elkoff the biggest electronics retailer in the Nordics Bink building next generation bank and Justin for Okay All right, so it's also going to be a very non boring week if you are a linker D enthusiast here at kubcon I've got a whole bunch of talks. You actually should have a piece of paper that'll list a bunch of them, too To all point out here later in this conference linker D maintainer Kevin Lime cooler It's going to talk about how linker D achieved some of its zero config Powers and then on Thursday service mesh at scale you can learn about how Xbox cloud gaming uses linker D To secure 22,000 pods around the world But of course all these talks are really exciting and I recommend that you join them So think speaking of exciting we are here because we think the service mesh is exciting at least I hope that's why you're here You know otherwise what are you doing with your life and it's natural for us to talk about how exciting the service mesh is And what you're going to hear the rest of the day is about these exciting features and the exciting new use cases and all Of the fun stuff we get to do and that's okay You know, that's fine like we can geek out about service meshes because we are implementers and we are enthusiasts We can geek out about performance, right? We can geek out about resource consumption and most importantly we can geek out about all of the cool crazy things that we get to add To the service mesh And I don't know where I found this image, but it really is remarkable if you if you stare at it for a while, right? but our Service mesh adopters don't actually want the service mesh to be exciting They want it to be boring right we might like the excitement But if you are the poor soul who has to actually operate the service mesh You want to be boring boring means you don't want it to have surprises. You don't want it to you know suddenly do something unexpected That's never good Boring means you don't want to have to go through a bunch of scary Tasks to keep it up to date which I mean tame it or to keep it healthy Right and boring means that you don't want to have to wake up at three in the morning and thinking about it's my service mesh Okay, right do I have to hire someone to deal with this thing? That's the opposite Okay, and we have a very particular strategy in the linker d project for how we address that and how we make things boring You know we make it simple right? That's that's our that's our secret right and and and we talked specifically about Simplicity so as you use the adopter of the service mesh you the operator What does it mean for linker d to be simple? Well one thing is it means linker d is observable every aspect of linker d is something You should be able to see and measure and record right? Means linker d has got to be understandable You should be able to break it down into its little components and you should be able to understand how each one works And the documentation should be clear and like that design should make sense and finally linker d should be predictable Right if you expect it to do something it should do that thing if you expect it to never do something It should never do that thing right and so here's our here's our top secret I can't believe I'm giving this information away and here's our top secret design philosophy number one do no harm Right, so if you have an application that is running and you add linker d to it The application should continue running sounds incredible, but that is actually quite hard to achieve second You want to be kubernetes right so we're all adopting kubernetes whether we like it or not We are stuck using kubernetes linker d should feel like kubernetes. It should smell like it It should be as close to kubernetes as possible third make the data plane awesome Right like this something very unique the linker d. I'd love to talk a lot more about this But this is a big part of of linker d's goal of operational simplicity And of course fourth we want to be modular and composable if you go to the workshop that is I think Wednesday about how we do cross cluster failover. I think it's a really nice example of how we came up with a really modular architecture there Finally boyant has introduced fully managed linker d. This is our ability to basically treat linker d as a managed service I'm really excited about this. I would also love to tell you a lot more about that. We're hiring You can find me at the buoyant booth out there or at the buoyant booth in kube con I'd love to talk to you about any of this stuff Have a great service mesh con. Thanks everyone