 Hey, everybody. Welcome to Service MeshCon 2021 Europe. Thank you so much for joining us today. So I am Chris Campbell, and I was a member of the program committee, and that's why I'm here talking to you today. And we'd all like to welcome you to the conference today. And so I've been working with this wonderful group here alongside the people from the Linux Foundation to kind of put together the program today. And so hopefully it's going to be a great conference. I thought I'd start out today by doing a little sharing on my own experience with Service Mesh and how it's kind of come into my life. I was originally more of an application developer. I was doing full stack and front-end development for many years. And I was actually kind of doing a lot of learning on my own at home, trying out new tools, new processes, things like that. And I got started using Google App Engine and Heroku a lot. I really like those tools because they made me feel so productive. I was so focused on my application and I could kind of just let the complexity of deployment really get figured out by those tools. But the disappointing thing is I would be so productive when I was learning and building on my own, but then when I went into the office, I had to start dealing with AWS and EC2 and deploying the EC2. And there's all these complexities that start coming about. And Docker really made those problems seem solvable, right? It really like planted the seed of this idea as like, oh, we could actually build something like a Heroku, like a Google App Engine, but that I could use in the enterprise. And that was super exciting and super empowering because it's so nice as a software developer to be able to have the right tool for the job so you can feel so much more productive. So Docker really kind of entered my life and switched me and actually wore my Docker shirt today as kind of a throwback. It moved my focus from the application to solving this problem of how can we make it easier for applications for developers to get their software out there. And one of the things that really stuck out to me was this feature in Docker called linking. And what it let you do is create an alias from one container to another such that you could kind of create this communication channel between them. So you could say link a DB container into a web app container. And then the web app can just refer to the DB container as DB. It doesn't need to know IP addresses or anything like that. Well, it would need another port still. But it wouldn't have to know what address it was on the network, which was cool. So because up to that point, well, what that did is it kind of planted this idea in my mind because up to that point applications always had to kind of mutate to the environment that they were deployed in, right? We use config files or environment variables to set the connection strings for our dependencies. So you'd have to say like, oh, the database is at this address on this port. So it's either local host when you're doing development or maybe when you're here to put in the cloud, it's a DNS name or another IP address an off-box machine. And so you'd always have to kind of be able to mutate. And this linking thing, and now I didn't really solve the problem, but I just planted this idea of, oh, maybe instead of the application always having to mutate to the environment it's deployed in, maybe we can get it to the point where the environment can mutate to the application. Maybe the infrastructure is where this problem can be solved. And I think service mesh is particularly well suited to add these types of capabilities. So when I think of service mesh, I think of four verticals of connectivity, reliability, observability and security and all four of those things as it relates to network traffic. They're all things that we can handle at the infrastructure layer to make it that much easier for developers to make it that much easier to build high quality, high, highly reliable, highly secure software. And I'm just so excited for what the future holds for out for cloud native applications and specifically how the service mesh can be there to help solve them. So if we can switch back to my slides. So yeah, that's kind of a little bit about me and my journey. For today, we're going to be hearing from some great speakers. We're going to be hearing from the leaders of the service mesh space, which is great, get to hear their vision where their projects are going or how they see the space evolving. We're also going to hear from a lot of people building on top of service mesh, both for their applications at home or in the office. And then also a lot of use cases for service mesh in academia. So we're going to have a couple talks from people that are using service mesh in teaching and for projects inside of the academic world. So super excited for the the group of people we have speaking today for work cloud and see what came out. I didn't do any like post editing on this. So some of these things are kind of raw. So I apologize for that. You can see a couple of things that probably don't make a lot of sense out of context. But anyways, I thought this would be a kind of a neat sneak peek into the content that we're going to see today. So service mesh is right there in the front. Perfect. Means we're at least a little bit on target. We got Linkerd, Istio, Envoy, great. Sounds like we're going to be hearing quite a bit about those things, which is awesome. Kubernetes, VMs and multicluster, excited. So we got some hybrid environments potentially. And also multicluster, right? It's going to have multiple Kubernetes environments, which is something my team's tackling soon. So that should be pretty cool. Chaos, right? Oh, there's a lot we could do for chaos testing and service mesh. I can see it. Monolithic apps, microservice architectures, based service mesh. That's awesome. Security posture, automatic mutual TLS. So a good amount of content here today, which is this is already kind of getting my mouth watering a little bit to hear what's going on here. So pretty exciting. Category wise, so we definitely wanted to get a little bit of stuff that's like under the hood and technical. So we're going to hear about core development and security. We're also going to hear about performance. We definitely are going to be, I'm sure is more and more people are adopting this in production. They're going to be more worried about like what performance tradeoffs am I making with service mesh? So we're going to hear about that. Like I mentioned, I'm excited about multicluster. So we have, I think a lot of people, a lot of other people are as well, because we got a lot of talks on that. And that's definitely been kind of a buzzword in the communities lately that I've seen monitoring, right? It's key. I think it's probably one of the most important pieces of service mesh is getting that visibility, you know, what's happening with your applications. And then lastly, we wanted to save a lot of space for production use cases, right? We have way more people adopting service mesh and getting it into production. So I'm super excited to hear about more production use cases. Lastly, I have a few shout outs. I want to say thank you to Lindsay and the rest of the Linux Foundation. They have been critical in putting together the conference today. I can probably say safely on behalf of the whole program committee, thank you to Lindsay. She really made the process super clear, and she really led the way to get everyone together and organized. So thank you so much to Lindsay. I'm sure there's a ton of people working with her at the Linux Foundation. So thank you to them as well. There's a lot of work that goes into putting these conferences together, especially in the times of COVID. So thank you so much to them. I'd also like to say thank you to Kong. It's critical that we have sponsorship for these conferences as well. And thank you so much to Kong for stepping up and being the diamond sponsor for today's conference. And I think we're going to hear from them shortly. I'll just leave with kind of one little parting thought. It's been a long journey, I think, getting service mesh out there, starting to unlock some of these capabilities. And sometimes it can feel like we're moving kind of slowly, right? I mean, I think I have these first kinds of thoughts, and we're playing around with the ideas of what we can do with sidecar containers and whatnot, like six years ago, maybe. So it kind of feels like it's going slow sometimes. But I always remember the saying of if you want to go fast, go alone. If you want to go far, go together. And I think we're going to make it pretty far as a community. So thank you, everyone, for joining us today. I'm excited for what the future holds. And I'm more excited about the conversations that we're going to have today, meeting with sub-like minded people, trying to solve some of the same problems. So I'll catch up with the rest of you inside of the talks. All right, have a great day.