 Hey, folks, hello and welcome. My name is Jason, and I'm here with my co-host, Catherine. And today, we're going to be talking about demystifying cloud-native concepts for the business world, which is a mouthful. But what we're really here to talk to you about is the Business Value Subcommittee for the CNCF and the work we're doing to try and translate some of the technical concepts to business leadership. So like I said earlier, I'm Jason. I'm one of the co-chairs of the CNCF Business Value Subcommittee. I work at Boyant on the LinkerD project, along with Catherine. Yeah, and so while we both work at Boyant, our journey started long before that. We both run the Kubernetes Meetup in DC, where we decided to write a series on the cloud-native landscape for the new stock. And that led to the creation of the CNCF business subcommittee, sorry, Business Value Subcommittee. And only most recently, we started working together at Boyant. And so basically, ever since, we're having a lot of fun at work, but also at our site projects, including the one we're going to tell you about today. All right. So just to get started, like Catherine said, we met working on the DC Kubernetes Meetup. And it was a really good experience. And what we found was there was a lot of confusion around some of what the various projects and products in the cloud-native space really were. So at the time, Catherine was already working with the new stack, writing articles about various cloud-native concepts. And she was just beginning work on a series to talk about the cloud-native landscape and make it go from this scary picture that you see here to something that's easier to digest if you're not already deeply indoctrinated in the cloud-native tools. So Catherine asked if I could help out. And so we agreed to start doing the series and basically do one article per column or per layer, depending on which way you're looking at it, that talks about, say, take runtime. We talk about what the runtime is. What is cloud-native storage? What are the products there that matter or don't matter to you and why should you care or not? And so as we wrote it, our goal was that even if you weren't already an engineer or already familiar with the cloud-native space, you're already an expert in Kubernetes, we wanted folks to be able to read and understand what we were saying about these layers. And so we ended up getting some really positive feedback from a lot of different folks, whether it was on LinkedIn or Twitter or actually from the new stack folks themselves. So it gave us a sense that this was actually a pretty important set of things. And we realized that this is really the type of content that the CNCF should be providing. We think they should provide the tools to get a shared understanding of what this stuff is instead of just the tech. At the time, Catherine had already been working pretty tightly with some of the folks over at the CNCF about various marketing concepts, and she saw the chance to start our own committee over there at the CNCF that would specifically target how do you translate the business value of CNCF projects to the broader public? And so that's how we got started. Over to you, Catherine. Yes, and so we kicked off the business value subcommittee with the goal to translate these cloud-native and CNCF projects to a larger audience. So why do we think this is so critical today? First of all, technology has really become a strategic differentiator. Most businesses have a digital presence, and for some it's even the only way they interact with their customers. And at some point, maybe even today, customers will not tolerate any more businesses that don't allow them to buy, book, or make a reservation online. They really demand that convenience. And because of that, technology has become really business critical, and that means that people on the business side are increasingly involved in strategic technology discussions that will impact our organizations for a year to come. And to make these types of decisions, they have to understand the technologies, right, and as well the impact they have, even if it's on a high level. So in short, the world has changed, and so have the requirements on executives. And we're really in a world that's calling for tech-savvy business leaders. But if you look at the content out there on Cloud Native Technologies, it's mostly targeted to technologists, and it's almost impossible to understand without a computer science background. So our mission is to start building that content and make the CNCF a reliable source on the topic for business people, just as it is for technologists today. And that's a pretty ambitious goal. So the question is like, how do you even get started? So to explain those concepts, we need to find a starting point, and that's why we started with a glossary, and Jason will tell you a little bit more about that. All right, thanks, Kevin. Yeah, so I'm actually gonna step back in time a little bit, right? We had our first couple of subcommittee meetings, and it was great. We had 30 plus folks would get on, talk about various things that we could create. There was a lot of energy and a lot of excitement, right? And that was awesome, right? But what we ran into really quickly was an understanding that we weren't all using the same terms in the same way, right? Like I might talk about a canary release, and someone else would be thinking I mean a blue-green deployment, right? Or do we have a shared understanding of GitOps, right? Or whatever that thing might be. Turns out a lot of these terms, your definition of them is a bit subjective based on where you work, what sort of role you're in, right? And in order to create a shared understanding between folks, having a shared language, having a shared lexicon is extremely important. And so we thought, hey, listen, why not build, why not build these new projects or these new products for the CNCF on the basis of a really strong foundation, right? And that foundation is this glossary. So if we take, as an example, the term service mesh, where I might use it in one way, someone from another project or another company might use it in a different way, right? And we wanna ensure that we have that shared definition, we also understand where a service mesh begins and an API gateway, or a service mesh ends and API gateway begins as an example, right? And so again, that's where the glossary start coming in really handy and to get the best definitions we possibly could, realize that we needed to crowdsource them. So building the glossary as an open source project allows us to all go in, have open discussions, raise issues and track changes over time to these documents. So I'm actually gonna go ahead and pull up the Git repo real quick. So here you see the glossary, right? You can find us over on GitHub, you can see what work's been done. You can see that they're reading me, you can go into the definitions folder, just take a peek at what's written, what still has to be written on that note. If you're looking to pick something up, please come over here into issues, grab something, grab the various terms that are important or that need work on. Love to hear from you in some of our discussions as far as like, hey, what terms are really important? Is this a good structure for a definition? And then of course, if you wanna contribute, come do a pull request. If you're confused by that process, please reach out to us on Slack, happy to walk you through it. We've done some documentation, but we're also happy to hold your hand as you get started with Git so that you can contribute a little bit. And so with that, I'm gonna hand it back over to you, Kevin. Yeah, so let's look at our service mesh entry as an example. So this is the format, right? But please note, it may change. We're always tweaking and improving it, but our goal is really to make it as user-friendly as possible. So we decided to break it down into three sections, what it is, the problem it addresses and how it helps. And when explaining a term, we wanna zoom out first and kind of create the context for people who may not be familiar with these technologies, right? So in this case, we're saying that it is, that we're dealing with a lot of small app components communicating over a network. And we try to use examples people can relate to, right? And then, so this network is kind of similar to your Wi-Fi network. It has the same challenges. So really kind of bringing these things home make them more tangible. And once we've explained what it is, we dive into the problem it addresses and how it can help. So yeah, this is the current look and please check it out and provide feedback. And yeah, I mean, if this sounds interesting, we would love you to get involved. Help us to make this an awesome cloud-native glossary. Let's demystify all these buzzwords, make them accessible to anyone who's interested. And yeah, like whether you're a technologist who enjoys breaking this concept down or if you're on the business side with a solid understanding of the space and can really empathize with people just getting started. You may still remember how hard it was for you and that's really important when creating this type of content. So where can you find us? Of course on GitHub, you just saw what we're, like Jason just pointed to it. You can get started right away with first good issues. You can also just first get into a conversation on Slack. You can reach us on the CNCF workspace. You can sign up for our mailing list and you can join our monthly meetings to get the invite, reach out via Slack or send us an email and we'll forward that to you. Yeah, great, thank you, Kevin. So what's next? Bit of a call to action here. We're looking to add more terms to the glossary. We're really hoping that folks here attending this conference are gonna be interested in looking at the current definitions we have, seeing what they like, what they don't like and providing some feedback, ideally in a respectful way, either on GitHub, on Slack or wherever. Once that's in better shape and we've got the glossary moving and we're getting more terms, we're really looking forward to creating an ebook to go with that cloud native landscape, something that can be freely distributed by the CNCF to help people get a good sense of what this thing is and how it's useful. Beyond that, something that's very close to my heart is the idea that we could create a shared set of personas to help us understand who's doing what role inside of an organization, whether you're a vendor, whether you're a customer building out a platform, whatever that may be. Get personas that everyone can kind of agree on so we understand the roles inside of this space. And then beyond that, we'd love to hear from you. Katherine and I are not like the arbiters or the gatekeepers for what is a good way to explain some of this stuff to folks. So we'd love to get your perspective, get some new ideas. We'd really love to have you attend our meetings and help us make cloud native really accessible to everybody. And with that, just wanted to say thanks, appreciate y'all taking the time to watch this with us. You can find me on Twitter at our days Morgan. You can find Katherine on Twitter at at CAFPAGA. And yeah, I think now it's time for questions. Yeah, thank you.