 Cool. I guess that works. Cool. It's good to be here. So today I'm going to chat a little bit about, you know, I'm sure some of you have heard of Kubernetes before, has, yes, is that a yes? People have heard, yay. How many people have heard of the CNCF? Oh, it's better than I expected, because most people just have heard of Kubernetes, but have no idea what the Cloud Native Computing Foundation is. So, you know, like I said, I'll give a brief intro on myself. I'm heavily involved with open source for just about two decades now. Currently, I have the fun job of serving as the CTO for the Cloud Native Computing Foundation and also the executive director of the Open Container Initiative, which is all about building container standards. And also I serve as a VP at the Linux Foundation. But in a previous life, I spent about five years running open source at Twitter, started an open source company way back in a day around Eclipse when people like, you know, developer tooling, at least back in a day, spent time committing on the Gentoo and Fedora Linux projects and wrote a lot of JVM stuff back at IBM. But that's who I am. I've been heavily involved in the open source for a while, so currently enjoying now building out the Cloud Native ecosystem. So I will prefix something before I start is, so I do work for, you know, CNCF, CNCF is part of the Linux Foundation family of foundations for lack of a better word. A lot of people don't realize that the LF is more than just Linux. You know, how many of you have heard of Let's Encrypt? Yeah, right? How many of you realize Let's Encrypt is actually part of the Linux Foundation? It's like no one, maybe one or two. But, you know, we're essentially a group of efforts that span things from like automotive to cloud, which I help run. So I just wanted to prefix that before I get started. So CNCF is not that old. It's only a couple, you know, two and a half years old since I helped start the foundation. And it's been kind of a crazy two years for me because it's just been growing a lot faster than I expected. This is kind of a little diagram that shows, you know, when we kind of started the foundation in late 2015 or January 2016, not many people have heard or even, you know, knew about Kubernetes and then it kind of took off, you know, like a rocket ship compared to some of the other competing technologies out there. Also, I had the role of being involved in, I don't know how many people remember like the container wars, but essentially there was a lot of threats of, you know, hey, we're going to fork Docker and so on. And so, you know, we helped kind of stabilize that with the Open Container Initiative. But it's been essentially a crazy two years or so helping build these ecosystems. So I'll give people a little history of kind of what cloud native is. People get a little bit confused on, you know, what kind of technology we're trying to build. But if you kind of like go back to the early 2000s, maybe late 90s, it was very common for people to buy, not something mainframe, but you would buy like a spark box from Sun, right? And then you would like run your application on it and kind of be happy. But it was generally a very single vendor approach. You know, you'd run an app, runs on a single machine or big mainframe type thing. And essentially it was non-virtualized. VMware then came around in early 2000s and popularly is the notion of a virtual machine. So now you could stuff a lot of VMs, you know, on one box. Great, you're utilizing more of the hardware. Everyone's happy. You could even run different operating systems. Eventually, AWS came around and popularized the notion of infrastructure as a service when they launched, you know, EC2 and S3 and all that jazz. Heroko came around and popularized the notion of platform as a service, right? So you could, you know, beautifully, you know, get your application, get the associated build pack, get push, magically launches. Then kind of the open source version of these things started to come along. So OpenStack helped pioneer the notion of a like open source infrastructure as a service, which was super cool. Cloud Foundry went and pioneered an open source pass. It was kind of the first major open source pass, great set of technology. And then, you know, for, you know, people weren't aware containers as a concept have kind of existed for quite a while, but it wasn't really until Docker came along in 2013 that they really popularized the notion of containers. And I think a lot of that came to, they were able to provide a great experiences for developers, so they had the Docker registry, which was super easy to like package and share things. And essentially took, you know, really things took off after that point. CNCF was really founded in kind of late 2015, 2016 to kind of help bring together these technologies kind of under one neutral foundation. But if you kind of look at the history of this, the cool thing about it is we started in an environment that was very single vendor. Everything was kind of a closed ecosystem. And over time, the arch of time, you know, since open source has gotten popular, is we've moved to multiple vendor, multiple, you know, kind of implementation ecosystem. So, you know, there's a lot of vendors collaborating on these open source things and it's all done in the open, which to me is kind of cool to see over time. And I think we're going to continue to see that trend happen in other kind of verticals, not only just cloud computing. So what exactly is a CNCF? You know, we're founded in late 2015. You know, the funny story of kind of how I started the job is, you know, I spent five years at Twitter kind of focused on their open source efforts, particularly around the infrastructure. We were running containers at Twitter before they were even cool or even people called them kind of containers. So I had a lot of experience. And what happened was Google open source Kubernetes and they're like, hey, we want to build, you know, a foundation around this. We don't want to be the full, we don't want to own the full thing because they realized if Kubernetes was going to be successful, it cannot just be perceived as Google controlled. They need to open it up, make sure it's neutral, put the copyright IP in a foundation and get other companies to contribute. So we did that. And so for me, after I quit Twitter, I was going to go travel the world for about a month and kind of just take time off after that crazy experience. But eventually I got a ping from the friends at the likes foundation like, hey, Google wants to build this crazy foundation. Do you want to do it? I'm like, sure. I've always wanted to try to build an open source foundation from scratch. So why not? It was a fun experience. Essentially, CNCF could be thought of something like the Apache Foundation where, you know, but we're essentially a collection of open source projects, but it is a very set of high quality curated cloud native projects. And when I say cloud native, it has to do essentially something with containers orchestrate. It's getting a little, I wonder if it's my phone. I will turn this off. Sorry. Let me see. It could be my phone or it could be the settings, but maybe I'll turn this off. So, you know, like I mentioned, CNCF, we're there to kind of curate a highly, high quality set of projects that are useful for folks. So, you know, and our goal is, you know, you're never going to be able to necessarily download like a Kubernetes distro from the CNCF website or any distro for our projects. We essentially want to allow our member companies to build cool distros, products, and so on. So that's kind of how we operate, which is kind of similar to the Apache Foundation. So, you know, like I mentioned, we're essentially a community of open infrastructure projects. Obviously, Kubernetes is our big one, but I'm sure some of you, if you're using Kubernetes already, you probably have dabbled with Prometheus somewhere in there, right? Because you're essentially wanting to monitor your cluster. Some of you may even, you know, wrote services that use JRPC. So, we have a collection of these projects that are independently useful on their own, but, you know, work really great if you combine them together in various ways. But we essentially don't force any of this integration. We have a variety of members that are part of CNCF. One of the cool things, at least from my perspective, that for the last two and a half years, I've been trying to essentially get all the cloud providers kind of working together in like a neutral setting. And so, you know, for like, I think the first time in history in like open source land, we have all the kind of top six or even top 10 cloud providers in the world from like Alibaba to AWS all working together in the foundation to kind of, you know, collaborate and move the state of cloud native forward. So, you know, Kubernetes, everyone's excited about it. Finally, after all this time, what is everyone exactly necessarily excited about? Well, for people that aren't aware, Kubernetes is kind of a weird term, but essentially it's Greek for, you know, pilot of a ship, essentially a pilot. So, you know, essentially, you know, the original idea behind the name, depending if you talk to some of the original people associated with the projects like bread and burns, essentially, you know, it was always meant to kind of represent, you know, essentially a pilot of a set of like applications or containers running in production. So, that's kind of where the name came from. But, you know, one unique aspect of Kubernetes has been just kind of how fast the project has been being developed. We have this kind of cool, you know, open source project that we developed to kind of track the velocity of how, you know, fast projects are being developed. If you go to github.com slash CNCF velocity, you kind of generate these charts on your own. But it's a logarithmic, which could be a little bit confusing for folks. But Kubernetes essentially ranks number two behind the kernel in terms of like velocity of issues, pull requests, contributions being handled. So, it's kind of unique in that regard. And, you know, it's always interesting to see some of the other projects here. If you look at like others React, there's also Homebrew. So, it's crazy to see how things have evolved in terms of how fast things are going. Which, by the way, like completely makes managing stuff on github a huge pain in the ass. We wrote some cool tools, but I could talk about that, like hallway track or something later if people are interested. So, what does Kubernetes actually do? You know, why is it so popular? It really kind of solves the problem of, you know, it abstracts away kind of the underlying hardware and resources associated with running, you know, software, you know, it basically, you know, I don't like the pets and cattle analogy, but essentially, it really makes, you know, makes it generic in a way where you don't have to worry about necessarily machines. You're essentially writing a service that, you know, has these dependencies and so on, and it kind of handles the distribution for you. You know, kind of the best analogy I like to use is some people may be familiar with POSIX, but, you know, in the way POSIX essentially allows you to write, you know, a script that will work across different, you know, OSs in some ways. Kubernetes kind of does the same concept for distributed applications. And, you know, under the covers, you know, I kind of like to use the analogy, well, this may not be the best one, but like, you know, Git, you know, a lot of people, I'm sure banged their head when they were first starting to learn Git, right? Like, oh, it's a little bit confusing, but under the covers, Git is actually fairly simple, right? There's only like a, you know, a handful of object types, right? You know, there's trees, you know, you know, blobs and so on. Kubernetes is pretty similar in, I think the learning curve is a little bit steep, but under the covers, you know, there's kind of a fairly somewhat simple, you know, object model, you know, there's pods that essentially, you know, serve as like the basic building block for Kubernetes. There's deployments, which, you know, how do you actually deploy things, pods could have services, and there's kind of a NAEP space in terms of how you categorize things. And a lot of tools are built, you know, you know, kind of using these concepts from Kubernetes. The same way like Git, if you look at kind of, you know, all the different command line options and tools out there, the porcelain commands are all kind of built off those like four objects, kind of the same principle here, I think applies for Kubernetes. So it is a bit of a steep learning curve, but once you get it, you're like, okay, kind of makes sense. You know, what are some unique features of Kubernetes? Why are people using it? You know, so, you know, obviously the whole like, you know, self healing automatically schedules, automatically scheduling of like containers of something like a service goes down. It's like a huge aspect for Kubernetes. The kind of bin packing of, hey, I want more services to run on a machine utilize more resources is a huge driving requirement. I mean, it's one of the reasons you look at kind of a large internet scale companies out there like, you know, Google, Twitter, Facebook, they're all doing the same thing of basically trying to cram as much, you know, software on each machine to be able to utilize all that hardware because if you're running this stuff at scale and you're only using, you know, 60% of your CPU or 20% of your RAM, that's a lot of wasted money, especially if you have support, you know, hundreds of millions or billions of users. So that's why people are doing it. You kind of have the auto scaling, rollout features and so on. So it's basically everything you need to kind of really build distributed applications. You know, the other thing I'll say is there are other talks today. I've saw that people are doing like Kubernetes tutorials and other things. So I highly recommend attending those sessions if you kind of want to get a quick, easy start with Kubernetes. How does the actual development work inside the Kubernetes community? Easiest way I could explain this is, you know, Kubernetes is kind of broken apart into what they call special interest groups. So if you wanted to say, hey, I want to contribute to the networking features in Kubernetes, you would join the networking special interest group and, you know, that's kind of how they participate. So they kind of try to, you know, spread out the work of, you know, focusing on specific aspects of Kubernetes and leave that, you know, leave it to the special interest group to control those specific things in part of the Kubernetes repo. So there's interest groups for all sorts of certain aspects. So this is generally, you know, how you would necessarily get involved if you were interested in contributing to Kubernetes. Pick your special interest group and go from there. As I mentioned before, there are kind of talks later in the day that people are doing tutorials, but if you kind of wanted to get involved with Kubernetes and learn how to play with it, I generally recommend people start with Minikube. It's a super easy way to kind of just get a Kubernetes cluster working on your laptop. You know, the other thing to note is almost all, like basically the major cloud providers all do kind of like a, Kubernetes as a service or managed Kubernetes offering. So you could start there, but Minikube makes it super easy to get things working on your laptop. If you're interested in contributing to, you know, the Kubernetes and CNCF community, we are participating in summer code right now. So, you know, if you happen to be a student and you're interested in contributing to one of our projects, go to github.com slash CNCF slash SOC, and there's a bunch of project ideas there. So the other thing I'd like to say, like we are more than just one project. You know, a lot of people are like, oh, you're just like the Kubernetes Foundation, they're like, no, there's a bunch of other projects that are super useful in CNCF. And so what we've done is try to build some tools to help people kind of see the landscape for a lack of a better word out there. So I don't know how many people have seen this diagram, but you know, there's a lot of, let's say projects and companies doing quote unquote cloud native things. So we've tried to build this out just to like, we used to track this stuff in like a Google Sheet and it was just a nightmare and we're like, well, how about we do this like in an open source way where we create a repo and help the community track it for us and build this out. And it's been pretty successful. So people love it and hate it, but it's useful at least for us to show, you know, here are the projects that we have like in like the, you know, networking space or the service management space. And here are the different products and projects out there. So it's a fun experience, but you know, it's useful to kind of see how sometimes complicated this stuff is. What's really cool recently is we created kind of an interactive version of this. So I don't know how many of you have seen this, but if you go to l.cncf.io, you can essentially filter and search for things. So you could, for example, let me see if I could find this. Do, do, do, do, do. I just opened it up. Let me go find it. Let's see, I'll just go back later. But essentially you could filter by like, hey, I want to see all the projects that are like in China or something like that, right? So you could totally do that. We're also doing some interesting things in serverless. So like sometimes our landscapes kind of dive down into like storage or networking related things. So if you go to s.cncf.io, you can actually go see like, here's like all the crazy like serverless projects out there that people are building either on top of Kubernetes or on other kind of cloud-based systems. Let's see, where am I? Trailmap. So another interesting concept is when people are essentially moving to, to take advantage of Kubernetes or moving to cloud-native, there's usually a lot of confusion in terms of like, where do I begin? How do I start? Which projects to use? So we heard a lot of complaints out there and like, well, you know, when I was younger, we used to kind of have like these like, you could have like a little trail map, right? And kind of follow along. And so like we try to do something, we try to kind of take that concept and apply it to cloud-native. So we've built this to basically, you know, show that there are many ways and paths to kind of becoming, you know, cloud-native. And for some people, that may generally start with containerizing your applications. For some people, it could be, you know, you already have CI CD set up, so you could start there, you know, eventually you get to orchestration and oh, I need to be able to observe everything within my clusters and here are some useful projects. So we essentially created this as a fun little diagram slash tool to kind of help people along their journey. So whether it's useful or not, I don't know, but we were trying to kind of simplify things for folks. So there's kind of a full journey that kind of goes through in terms of our opinion of what people would take advantage of as they become more cloud-native. So feel free to take a look at it. It's all online, so you could, you know, contribute to it, you know, pull requests, issues are always hopeful and welcome. So I kind of will wrap things up and hopefully leave some time for questions because that's always more fun. So kind of wrap things up. So a couple of trends, you know, that I want to kind of mention before I kind of, you know, end things speaking about like where I think cloud-native is going is open source is super popular. You know, the previous presentation, you know, there's, as was mentioned, like three kind of distinct phases of open source and, you know, things are going on. Like, you know, it's actually crazy to see like almost, you know, if you have a TV at home, there's a huge chance that it's using like open source software, right? Everyone has phones, you know, even your Apple phone has open source on it. Android is essentially Linux, you know, with some stuff on it. Cars are shipping open source software. So, you know, it's, we're going to see open source to be prevalent, you know, all around us. And I think this trend will, you know, continue. There's some studies out there that have been done where it says like, oh, 78% of companies are using open source. I think that number is much higher. I think they just do like companies that aren't aware they're using open source. But the cool thing here is I think 63, it says 63% of companies are starting to participate and actively contribute to open source, which I think is important because, you know, open source is only sustainable if people actually contribute and give back. So seeing companies do this, whether it's like actually contributing patches or financially, physically supporting projects they depend on in communities, they depend on is clutch. The other kind of trend and kind of where CNCF came from is a lot of the internet scale companies out there like Twitter, Google, Facebook have basically open sourced a lot of how they do their infrastructure, right? You know, TensorFlow, basically how Google's handling AI. Netflix is basically, we're gonna open source everything in terms of how we run because at the end of the day, we make money by letting people watch movies and TV shows and so on. We're not a software shop, we don't sell license to software, so we're gonna open source all the infrastructure so people could help us to make a better service. So this has been happening for the last, probably several or five plus years now and I think this trend will continue to happen and so what essentially it is, it is being paired with the trend that more and more companies are essentially using open source and becoming software companies. So folks like Mercedes Benz and Daimler are all of a sudden trying to figure out how to scale their infrastructure like inside each car is potentially running Linux with open source software that connects to some cloud that stores information and has some type of experience. So what they're gonna do is essentially copy or learn from how these original internet scale companies did it because Twitter and Facebook, Google, they all had to figure out how do you support a billion users, right? So you'll see this trend of other companies out there that are becoming more software related kind of use tools like Kubernetes and TensorFlow to benefit from their own. So that's basically kind of the trends here I think as more and more companies become software companies they're gonna use tools like Kubernetes, TensorFlow to take advantage of kind of the work that has been done before. So a couple resources to share before I open in questions. We have three big events in the Kubernetes and cloud native community. We have one in Europe coming up in Copenhagen. That's about a month, a little over a month away. We're doing our first event in China which is great, our kind of first event in Asia. It's in Shanghai in November. See how that goes, it's gonna be interesting. And then we kind of have our banner event in North America in Seattle in December this year. So, one important thing is we do a ton of scholarships for our conferences. So if some of you are students or essentially could qualify for a diversity scholarship I recommend you apply. We sent, at the last KubeCon we had in North America in December we had about 120 or so diversity scholarship recipients and we spent a quarter million dollars in bringing them. We've raised a lot of money to do that and it's something we're proud of. So please apply. We'd love to see some of you at our event. And then other than that these are just like random links that you could click on to learn a little bit more about the Kubernetes and CNCF community. So don't know how I'm doing on time but I want to thank you for giving me the opportunity to speak with all my talks. If you learn something new I'm very happy. So hopefully you did. If you need any help with Kubernetes or any CNCF related thing please feel free to shoot me an email or tweet. I'd love to kind of learn if you're using any of these technologies and if you want to get involved in our communities I'm more than happy to take the time to lead you through that. So thank you again and hope you learn something new. Thanks Chris. Don't go away.