 So before we start again, a huge round of welcome to everyone that's contributed. These are just some of the names that we have here. But the Argo community as a whole has grown a lot. And there's a lot that we have done that will come a long way. So I usually start with one of the key stats that we want to talk about. So we look at the number of contributors. Phenomenal growth in the number of contributors, and this is just in the last year. Over 33% growth in the number of people that are contributing to the project. In all shapes, forms, right? It doesn't take much to contribute to Argo. By the way, even if you don't write code, I was watching so many document mistakes last night. I was itching to start correcting all of the mistakes. So you can do that as well, by the way. If we start looking at the number of stars we're growing, I really want to see it get to 100,000. So please talk to your friends, families, everyone. Start moving. I mean, sometimes I look at this and I say, you know, with the amount of growth and the number of people using it, why are stars not growing? And I think someone told me, like, oh, it's Leslie Fair now. You know, Argo's successful, so we don't go and hit the start button anymore. I'm like, okay, but I'd still like to see it go there. And then we look at the number of forks, right? Again, if you start looking at it, this is phenomenal growth, right? So huge round of applause to all of the contributors, to the community, because without them, this would not be successful, right? Also, I think Argo was kind of unique in the way we started, you know, looking at who was actually using Argo. So if you're familiar with the Argo GitHub repo, you know, there's a file there. And we asked everyone that was using Argo to go in and publicly reference themselves, right? So in 2022, we had 380 companies that actually publicly referenced themselves saying they were using Argo. A lot of names, brand names. And as I look at it today, 2023, the numbers grown, we now have 400 or 500 companies almost using Argo, right? So the growth of this is amazing. And then if I start looking at the number of institutions that are represented, it's again huge, right? So when I start thinking about this and I talked to a lot of the contributors, this is all because of you. This is because of the community. It's also because of the product. And I call Argo a product, by the way. I know it's an open source project, but we've always looked at it as it's something to be consumed by everyone. So how do you build it in a manner that actually looks like another product? And that includes everything. It includes the resiliency, the safety, the user experience, you know, how do people get on board it? How do people come together? So this is really, really good. Again, huge round of applause, please, thank you. Now, this is the first year that Argo actually has been a graduated CNCF project. So in the first year, you can see we have seen a number of things. First of all, it is the third highest project in terms of PR authors, okay? We now have over 245 contributions to the project. Again, this is huge, right? And it's not slowing down. We see a tremendous amount of growth as we're growing. But when we start looking at what is it helping, how is it actually helping everyone innovate? And actually, and all of you come from very, very different companies, different spheres, different domains. And the fundamental things that we start with is the first thing is reducing deployment issues, right? Faster detection. If you start looking at the observability metrics that we have been put into Argo, being able to look at your environment and detect issues. This is really the fundamental thing. I'm representing, of course, into it here. It is, we use Argo everywhere. But this is the one thing. One of the things that we measure is our mean time to detect issues across our deployments. And we've seen a tremendous increase in how fast we can increase and detect issues, whether it's in deployment, production, as we move faster. The other thing is actually increasing the velocity. As companies, more and more companies start thinking about their cloud-native deployments and really building the platform on which all of their products are gonna run, this is gonna become important, right? How do you take all of your developers? We have 7,000 developers that into it, for example. How do I make them fast? How do I make them really, really productive without really understanding all of the things that they would have under the covers? So these are some of the things that I find as I talk to the community and I talk to all the leaders. What Argo is really helping them do, Argo CD in particular, is really about making things fast, really reducing the burden from the developers to deploy faster, to deploy with confidence, to deploy with security in place. And then the last thing is really about abstracting. Because as you get bigger, as you start having these deployments, it's still hard. Kubernetes is not easy still, when you start deploying it in large environments. So really how do you abstract the key concept in the services and abstractions and experiences from your lay developers so that everyone doesn't need to know what a pod disruption budget is or how are you gonna auto-scale it? So this is one thing I think that we need to start focusing on because the deployment portion that Argo does is amazing in order to be able to do this. But these are just some of the ways where we're gonna make it a lot easier as we move forward, okay? So what have we done over the last year? There are a number of things that I wanna talk about, right? I talked about Argo being a product. Last year, we actually focused on resiliency and security. In particular, we achieved the, what I call, by the way, SLSA I learned, earlier this year, it's called Salsa. It's our supply chain level of software architects, right? Artifact, sorry. But we achieved level three provenance last year. And this was done by the CNCF, we actually was conducted in an effort by the CNCF to actually take Argo CD, put it through its paces, through external organizations to figure out how secure it was. And there's a number of things that we did last year, right? We have adopted the open SSF scorecard. We actually utilized the CLO monitor security score of 100% last year. And this is again to give enterprises the confidence that it can be deployed in production with all of the governance and security artifacts built in. There's a lot of other things that we have done along the way. But when I start thinking about platforms and platform engineering in particular, what I talked about is extensions that we're doing. So last year we introduced our metrics extension, which allows you to look from an observability standpoint what is happening in your environment. How do you get plugged in to look at your environment and see what's going on? This is a huge, huge benefit for managing, if you're managing large clusters, you're managing large deployments, and you wanna see what's going on in those environments. The extension form, by the way, allows us to actually, allows the community actually to contribute different extensions in the long run, right? So this is how you essentially grow the platform and essentially grow the ecosystem over time, right? Our goal allows for you being rollback, roll forward, right? With, and I'll talk more about where we're heading next, but in terms of being able to look at analytics and do this is gonna be critical as well, okay? And the last thing is really around making it easy, making it easy for people to use to adopt. The UI extensions, the user interface extensions that we've done, these are amazing. By the way, this is what makes our goal so successful is that it has a very, very powerful UI and we keep improving it and extending it, right? So when I talk about product, the productization of our goal, our goal being a product, without all of these things, it would not be as successful, right? So again, thank you to everyone for everything that we've done. No contribution is small. Again, just a little highlight of all the things that have gone on in the program and the project and all the people that have been involved. Again, I urge all of you, if you have not made a contribution, why don't you make it a goal before you leave KubeCon, make a contribution to the Argo GitHub repository? Again, very simple, by the way, okay? You don't have to write code if you don't write code, but you can do a lot of things to contribute to the community, okay? And again, thank you for the community, okay? So what's next? Two things, I'll highlight two things that we do. You've all heard about GenAI, you've all heard about AI. AIOps is the new buzz in the platform world. And this is where I think we're gonna really start focusing the vision and the roadmap for Argo, right? How do we make it easy to do things like auto scaling? How do we do progressive delivery? How do we detect and isolate problems, right? How do we detect security breaches? There's a lot of stuff that we're gonna be doing here, which is gonna be very interesting, right? So stay tuned for this roadmap because this really is gonna set the stage for what we do in the next two years, okay? Secondly, when we talk about simplified experiences, abstracting all of the intricacies of Kubernetes and how you deploy and what you do, this has been a journey that we've been on and this we're gonna be doing a lot more. How do you reduce your ingress? How do you improve security? How do you left shift security into this thing, right? What about resources? How do you provision them? What do you do, right? How do you get visible into these things, right? So that's gonna be key, right? So these two themes are gonna be the focus for us as we head into it. By the way, it is being used a lot. Argo actually does get used in the ML ops and the AIOps community a lot today. And Argo workflows is actually a core driver for a lot of the ML pipelines that are driven in large companies today. So you'll be seeing a lot of this today, I know, and a lot of talks actually throughout QCon focused around this. Now, I also wanted to mention one thing. There's a lot that goes on. There's a huge community that is coming together. There is a lot of companies, by the way, of a lot of vendors that are actually productizing and using Argo today and helping customers, right? Make it big, right? And that's the goal. We really want this community to grow not just from a contributor and a maintainer perspective, but also vendors that are actually helping other companies to adopt Argo and use it and make it easy. So one of the things that we've done is we're actually starting a training and certification program. It was built collaboratively with a lot of companies, acuity leading the charge on this. So thank you. And it's in beta today. So please scan it, go to the beta program, get on board, we want to get it into production and really start a certification and training program for Argo, right? So this will help you and your companies. It'll help you as you look for jobs, maybe, but to have the certification behind you that you actually know and understand and how to use and deploy Argo. Okay, with that, I want to give it back to Dan, but again, a huge round of applause for our sponsors because this is a huge event. It takes a lot to run this. So thank you. I give it all to Dan.