 Thank you so much, Nikita, our new vice chair of the CNCF TOC. My name is Lin Sang Bangju, KubeCon Paris, I'm the head of open source at solo.io. As Nikita said, I'm also CNCF TOC and also the Israel Project TOC. Hi, my nickname is Dimps. I wave some hats in the community as well. I work for AWS and I'm part of the TOC with Lin and Nikita as well. So let's quickly get started. I know this is the last keynote and you're reaching to go back. So thanks for staying. So here are fellow current TOC members. We are the elected body in the TOC. So it's the Technical Oversight Committee and we have 11 people. We rotate, we have some new members including me, and this is my second round here. Nikita is our vice chair. We just create, go Nikita. Thank you. So if you see any of them, please have a chat with them and get to know them because these are your representatives in the community. So for the last few months, this is what we've been doing. There's been incubations and graduations. We've had a really good set of sandbox projects coming in. The TOC itself works on a bunch of things. One of the things we got started on, you heard from the folks working on the AI working group, those are the kind of things that we end up organizing through the TOC and the tags. We wrote down a lot of the things that we were doing somewhat ad hoc or maybe we were not doing it very consistently. We started writing those things down. Most recently, one of the things that we ended up writing down was, hey, if you're a project, then you need to kind of write down what is your expectation from, that the end users can expect from you in terms of releases. So we had a long two-day offsite in CERN, and thanks for the CERN team to sponsor the offsite, and the sum of the TOC members ended up going and visiting the large Hatteron Collider too. So it's always exciting. Thank you. Thank you, CERN. So the project's moving levels is consistently the restriction around it. What does it mean? What do I need to do? Is there a checklist? How do I go about doing it? How do I prep and things like that? So that is another thing that we ended up writing down as well. So going with the team today of reminiscences, so this is the architecture diagram from 2015. There's lots of things that are not there. There's only some things that are there. And in 2015, all these folks said some nice things when we got started. 2016, Prometheus was one of the things that came out. Kubernetes had a bunch of releases. And this was the first time in 2016 was you could get your swag, right? So the first one was definitely that Kubernetes won. 2017, Landscape Beard already had a bunch of things going into it. And the call out here is definitely to Chris Nova and Brand Brandt and a whole bunch of new projects that ended up getting started here. So this is by no means comprehensive or anything like that. This is my reminiscence of what was happening around that time. 2018, Knative, HED, and Kelsey and Sandbox Proposal, that's when we started having multiple projects coming into the sandbox and giving them a space to work in together. 2019, we started the tags. They were called six back then. And if you note a quote from Corey, I don't know if Corey is here this week. But 2019, he said, five years, we might not care about Kubernetes. So that's always fun to revisit. K3S made an appearance. And in 2020, we had SIG observability. And there are some of my favorite people here, including Ian. In 2021, EBPF came up and Cillium and a bunch of other things as well. So in 2022, Wasm turned around and made its appearance and a bunch of other things that ended up starting around it. So through this journey, we have grown to 184 projects. As of right now, you've heard the statistics today and hoping that we continue to grow and stabilize and mature and graduate. And in 2023, this is one of my favorite pictures. You can see how large the Kubernetes community ended up growing to. And one of the favorite release artifacts that we have for this was 129 is the Mandela. I really love it. Thanks to the Kubernetes release team for having consistent, stable quality releases out and helping us do it. So we are up and down, left, right. We have covered everything. And the guy is screaming. So knowing where we are, let's take a look at where we are going to go next. Thank you so much, James, for a fabulous overview of the past nine years. So what about next decade? I want you to think about in your head, what do you think? Tim Hawke can give an amazing next decade for Kubernetes in Chicago. And we were so inspired. So we reached out to the leaders in the TOC community and asked them, what do they think the next decade should be? What technology will continue to be hot? And this is the output of the survey. Not surprisingly, over 75% users said AI, sustainability, security, and edge computing will continue to be hot, along with web assembly and service mesh. What about the next big disruption? Think about in your head, see if you agree with us. Cassie starts with cloud-native AI. Chris is always looking ahead, the many of us. Wazm, combined with CNCF projects, will become the best runtime for AI and LMS. John believes simplicity is the next big disruption, which really resonates with me. Alex, talk about consolidation. How many of you feel we have too many projects out there that really need a consolidation? What about workloads? Workloads are the ones that really interact with our end user. Packers that talk about Kubernetes workloads are multi-clustered and needs to share data. And Jimmy talked about heterogeneous workload, non-traditional workload, and repurposed Kubernetes to support these heterogeneous workloads. And anonymous leaders talk about developers are so tired about endless complexities. And if that resonates with you, he really believes our service API is going to be the next big disruption. Penny is so environmental. Think about suspendability, waste removal, and overall optimization for our whole ecosystem. So where do you think the cloud-native is going in the next decade? Likely actually towards cloud-native. I really like this quote, because I feel in the past, we spent so much time building Kubernetes, building plugins that extend on top of Kubernetes so we can actually be cloud-native going forward. And Emily Fox, who is our TOC chair, believes we're going to see more strong in the ecosystem and integrate existing infrastructure out there. And Chris is always ahead. Cloud-native is becoming ubiquitous already on the server, but it's expanding to the edge and more. Konani believe we're going to see more work happening outside of the cloud. Cloud is well, and cloud-native is how. I thought that was really interesting about cloud-native is how. David believes cloud-native is going to be the commodity. I think that's going to resonate with many of you here for the next decade, similar to what VM was in the past. I truly believe we are not going to need to talk about Kubernetes, service measures, or even networking, because they're just going to be infrastructure. And I believe Dave agreed with me. He said stuff like service measures or web assembly would move towards where Kubernetes is today, so we don't need to talk about it. And another anonymous leader who is also a formal TOC member said, boring, useful infrastructure, this really resonates with me. What about AI? We can't talk about next decade without AI. Ali starts talking about enabling AI, period. And Daniel adds on to cloud-native projects is going to play a vital role in operationalizing AI workflows. Brandon added on to we're going to see more move towards be able to run the same workload and scale with much less footprints. And Vinay added on to cost and sustainability is going to be a big focus, and AI will be heavily used to optimize cloud spending. What about the users? I believe the users are the center of the stage, not on the list. We can't forget them. We're going to see plenty of consolidation. Cloud-native have always been the lead for the developers and the platform engineers. When Athena believes we're going to see more user cases around AI and new ways to applying AI to existing applications and sales service platform, I think that really resonates with me. We're going to see a lot of innovations out there. Priyanka believes we're going to see a portable, inter-optable AI stack is the cloud-native option. I love that. Now, do you agree with us while cloud-native is going? If you agree or disagree, we would love to invite you all to join us at the TOC panel, where all the other TOC members will be there, and the panel will be moderated by Chris. The panel is at 11.55 today. Thank you so much. Thank you all. Hope to see you there.