 and hippie hacker, you can join us for this journey. We're gonna talk a bit about the Kubernetes, particularly the journey we've been on together and how we're almost there. Some of our story starts in another community that I was a part of. Chef, I met some really interesting people at Chef. Adam Jacobs himself and Noah Penoitz, code ranger. Very unique and interesting people. Adam's very metal and code ranger is very community. They share some DNA around culture being super important. I joke that the revolution will not be televised. It'll be coded, not necessarily with Chef, but with all of the culture that operational code can bring. Crier's a place for us to chat about such things. And the hashtag here in front of Chef is for an IRC channel, which is where we used to internet really chat before things like Twitter were around. And there's a really good story about someone who came to our IRC chat wanting to impress their significant other with some cool food that they would prepare at home. And I loved how Noah came forward and included them and said, absolutely, we'll give you a hand. And that impressed me. And I carry that culture forward with me. And I think I also see remnants of that in the Kubernetes community. Thank you for Noah for bringing that forward and thank you for Adam for setting up a company where culture was so important. While I was working there, I got to work. At some really cool places that need some really cool people. One of them included working on boats, bigger boats, really big boats, cruise ship boats. And I got to work with a couple of people to help them deploy the cloud onto said boats. It was Aaron Crickenburger and Bob Wise. Onto these ships, be a satellite while they were at sea. We would deploy the cloud onto the hardware itself, which I found really fun and really interesting. And I thought about that for a while and I really enjoyed my time working with Bob and Aaron. There were things that were difficult about that time. One was that containerization was just coming into play. Salmon hikes and friends were iterating so fast and it made it hard to develop solutions on top of this technology. We needed it. Docker on the ships at sea. But we also needed a way to orchestrate that. I'm not sure if some of our friends at Google came into play and in their spare time, 20% time, I think they came up with Kubernetes and that helped to orchestrate beyond just having container engine that ecosystem that developed into something that was beginning to kind of coalesce into something extremely, extremely valuable to all of us. Now, we've got Kubernetes and we've got Docker. I realize that I'd like to play with that. So I began working with some of my friends and there are some servers given to us by Bob, same ones we deployed at sea. And so I worked with some friends of mine and we created a co-op. That's the Vulp cooperative. So it was myself and Lucina, Taylor and LaValle and a few others, but these were the core folks I spent my time with at Vulp. And we did some pretty cool stuff together. I've known Taylor for, well, since college we're a good old college buddies. And I ended up going back to New Zealand and tried to bring the servers with me, but I did not have the funds. It was quite expensive to get the servers over there. So I reached out to my friend, Bob. I said, hey, Bob. Bob said, hey, hippie. Said, can you help me get these servers over there? Said, no, but I know someone who I'd like to introduce you to. Said, I want you to meet Dan. Dan was working on a new Linux foundation thing called the Cloud Data Compute Foundation. And he said, I think hippie can help you with that. And I really thank you for the introduction, Bob. Dan was a real visionary. And he was thinking about how can we in this initial state just demonstrate what the cloud is? He worked on demo, cncf slash demo on GitHub. And slowly that evolved into things like cncf.ci, which my friends at Volk worked on as well. And when I was back in New Zealand, oh, down here. I found that a cooperative in New Zealand to kind of parallel the cooperative in the States. That's where I was born. And this cooperative ended up founding it with Denver Williams. As a teenager, he travels from New Zealand to Berlin to speak on Kubernetes. And he has since joined Volk and I'm super proud of it. cncf.ci has since been taken over by the Volk team. And between Volk and I, we do a lot of the strategic initiatives for cncf. This focus for this talk is all about certified Kubernetes. And last time I was in China, I brought a friend from New Zealand with me. Her name was Indigo Phillips. Now, Indy brought her culture with her on that journey. And she shared with us her pepihá. Now, her pepihá is her name and her home, her lake and her mountain and the place in which she meets with her people and the canoe in which she arrived on, her ancestors arrived on and her tribes. And there's another special protocol of introduction that she shared with us called the facapapa, which is the lineage of ancestors from that boat or that waka that first landed in New Zealand. And it's part of that protocol and that introspection of sharing the identity of who she is, Indigo Phillips, age 42, New Zealand Maori. Currently at that time, speaking at KubeCon, trialing to Shanghai and sharing her culture with the tech world. And the sources, the locations she's from are from Todanga Bay of Plenial, Thiruwa, where we're broadcasting from today. And Rotirua, which is about an hour from here, a lovely place, and there's a lot of parallels in that introduction that we suggested that maybe we do in our software world as well, where our software might say, here's my version, I'm currently talking to an API server, and here's the things I'm doing at this moment. The source and locations being functions inside of our code repositories to identify looking at the history, who would be best to talk to to help define what it is that we wanna test. Thank you so much, Indigo, for sharing your culture with us and influencing how Kubernetes is defined. Now, in order for us to have Kubernetes agreed on and defined by us as a community, we need to have people who can take a look at it first and say, that looks good to me. And we need people who can go through and approve it fully and say I am authority in this area, we can approve it. So I'm gonna add in a few of those people real quick. Hold on, Dems, Liget, Tim Hocken, and these were some of our LGTMers that said this looks good to me. So we'll put them here within our list of people who helped define what Kubernetes is as an LGTMer. And in addition, we had John Billomaric, Smarter Clayton, and Tim Hickson-Claire that were part of the approvers for a long time. And I'm super thankful that we got their slash approve on many of these changes. Those changes were made in part, if not mainly by our team at IEI. And I have them right here. Rion, Lionhounds, Caleb Woodbine, Steven Haywood, and Zach Mandel. So that we have all of these faces that are part of that wild journey that I've got to spend some time with and help define what Kubernetes is. One thing we noted early on in that journey is that Ken Michi showed up to one of the meetings, I believe one of the TOC meetings, and he's like, it's a governing board meeting. He said, do you know that we don't actually have tests for around 10 to 11% of Kubernetes? We were kind of in shock that that was true. And we looked and sure enough, he was right. So Dan said, let's do something about that. And so Dan shared a picture of his hard drive. This is actually a picture of Dan Kahn's hard drive with some software that scans the folders. He said, can we do something that might let us look at the Kubernetes API that might look something like this. And Rowan and some other friends at II were able to put together an image that looks like this. Very similar to Dan's vision or image of his hard drive called the starburst chart. And you'll notice that the end of the bar there's plenty of space in between and this is actually untested areas. And so at this point, when we finally got a graph together only 14% was conformance tested, which is pretty wild thinking that we all of our applications globally, all of our kube apps only had a solid surface area of about 15% to work with. But over time, we began to fill in those blanks. You can see here that they got a bit better over time. But this is for every possible API. And with our SIG architecture meetings and the people who can improve those APIs, we slimmed it down to focus just on the APIs that were required for everybody. And that means the stuff not within the red or the blue but only the green. So these are the APIs as they've evolved. Here was a 36% of just the stuff available to be tested slowly filling it in here over time here until we get to our most recent one. And this is what's looking really, really great. You see the amount of progress we've made and how very few items remain to fill in. And I'm super thankful that we are gonna get there this year. This is the year that we wipe out all of that technical debt. We can see that journey most clearly in our up into the right graph with all the release numbers here at the bottom. I'm really digging that we haven't had any more orange which was technical debt getting added. And we haven't had any regression. So that means that this is continually getting smaller and at this rate we'll be done within the next two to three releases. And that is very exciting to me. So by Q2, Q3, somewhere in there we should be pretty far along with squashing all of these out of the way. That is something I'm super excited and I know Dan would be happy to see. This is new endpoints I believe for 118. And they got introduced without tests and this is part of the gates that we have in place. And those gates are put in place not only for new APIs coming through but for new people submitting their tests. So it's been lovely to see tooling like Heptio Sonoboy being used to help people easily submit conformance results and collect them. But they are filtered through Robert and I have to move out of the way for a second. We'll help them up here through Robert Kilties, Rob Kilties and Furno Klein Hans's software that runs in Prow for helping Taylor Wagoner defend the certification. So if companies submissions run with Heptio Sonoboy get passed the gates defined by Rob and Furno then Taylor will give them the final approval and they'll have certified Kubernetes. So I hope you've enjoyed this journey and I want to thank each of you for your eyes and I want to do kind of a moment to remember Dan and Kurt Kahn, it was his vision and belief in each of us that inspired this program to come to being and I look forward to seeing this come to full fruition and erasing all of that debt. I'll see each of you face to face some day and eye to eye. Peace.