 All right, folks, I'm going to get started just a minute early, unless I get waved off. We're going to be talking just a little about the Argo project. How many people are familiar with Argo? Have heard of it? About half the audience, so maybe just a quick primer as we get through this. Just a brief intro here, Argo project is actually four projects. It's very unique in the CNCF because we're not just one tool. We're like a bunch of tools. Those tools are Argo workflows, which is very popular for doing data pipelines, machine learning. Any kind of workflow that you want to run on Kubernetes, Argo workflows has you covered. It especially has this amazing superpower to scale out and use the resources from many nodes, which is one of the reasons that it's so popular with data pipelines. Argo events is for general inventing off of Kubernetes. Something happens. You want to send an alert, trigger something to happen. That's your tool. Argo CD is a GitOps deployment tool, which I'll talk a little bit more about. Argo rollouts is a tool for doing canary, blue-green, progressive delivery. We recently ran a survey on these tools. We do a survey every year for Argo workflows and Argo CD. This year was the first time we've done Argo rollouts. How many people are familiar with NPS and what it means? Very few people. Okay. NPS is basically a score where you ask people how likely they are to recommend your product. An example of a bad net promoter score, it stands for net promoter score, would be like most internet service providers, you know the ones, they have a negative 40. That's a bad score, right? The iPhone, everybody loves the iPhone, it's like 50. Argo workflows is 27, which is good, it's solid, people really like it. Argo CD is 76, which is when you can get a compound and invite people to change their life. What does 76 means? That's a joke. It's okay. Argo rollouts is 35, very good as well. If we look at the star growth on these, and star growth is not a perfect metric, just compared to other existing tools that are out there. You can see Argo CD and Argo workflows very much accelerating in their growth and show no signs of stopping, which is very cool. Of course, Argo is super popular. Grandmaster, EA, Adobe, Google, Alibaba, GitHub, Robinhood, Intuit, Sumo, Major League Baseball, Peloton, Tesla, we have hundreds and hundreds of adopters. If you have not put your company name there, please go to the Argo repo and there's an adopters file where you can add your company on and you can show your love and support for the project in that way. Let's talk just for a moment about Argo CD. There's a tendency, if we think about CI and CD, CI is where we build, we test, we promote artifacts, CD is where we deploy, test, and rollback. Classically, CI has been overextended into CD. This is because you've got a workflow engine. You can script it out, so you do it, you shove it in there, and you start letting it deploy things, but it's not necessarily optimized for that. This is where Argo CD comes in. Argo CD gives you the ability to create an application. An application is a custom resource definition in Kubernetes, and you can define a source of truth in Git and a desired destination, and the application is essentially a policy for how that source of truth should be reconciled and pushed into deployment. So far, so good. This simple idea is entirely revolutionary, and it's completely changed the way that people deploy their software. If you're not using Argo CD yet, just starting here will vastly improve the performance of your teams. Now, let's talk for a moment about Argo rollouts. This is a tool that I think people are sleeping on. Do you guys know that expression? People are sleeping on this? It means like the world is happening outside, and you're asleep, and you're missing it. Argo rollouts is a tool that, for example, Salesforce, every single one of their services is using Argo rollouts. They're not using it with Argo CD, by the way. All these tools can be used independently of one another, so you don't need all of the whole suite of stuff. You just pick the tool you want and use the job. You can take inside of Kubernetes, you can take a deployment object, and you wrap it in a custom resource definition called a rollout, and you just say rollout and you reference the deployment. Then you can specify how you want it to be deployed. You can say, give 10% of my traffic the new version of my application, run some metrics, arbitrary metrics, check Prometheus, whatever, and if it looks good, keep going, and if it doesn't, roll back. This gives you a GitOps-friendly way declaratively to handle progressive delivery. It's incredibly powerful, and it is basically zero cost. Implementing Argo rollouts basically costs nothing from a time standpoint. I mean, it takes, like, I can do it in like five minutes. It's like that quick, so it's a game changer. Any Argo rollouts fans in here? Hand is helpful. I was looking like, woo, you know, like, because then everybody else is like, oh, well, they're really excited. I got to use it. All right. So a couple of things that we have coming on, integration. So backstage, obviously very popular, IDP platforms. You want to build your own IDP. Hey, we've got a plug-in for Argo CD, so you can actually get the status of all of your applications inside of backstage and build that into your flows. So that's a really nice tool that's available for you. Argo workflows, there's a number of different integrations. Kubeflow is very popular, but basically any workflow engine is going to work with Argo workflows at this point. I'm sorry we don't have more time to go deeper into those. So what's next for Argo? Well, we're working on Argo CD 2.11. We just released 2.10. We've just done some security updates and have been working through those, and we're going to be doing more work to expand the project. There's a number of proposals to do OCI as source of truth. So this would allow you to not just point at a get repo as a source of truth, but also point at an OCI repo as a source of truth. In addition to Helm charts, which we already support, right? We also have some additional proposals out for handling environment promotion. So hey, you know, I want to deploy to this application, and then I want to promote those changes up. And there's a lot of work going on in there in the community. If you want to get involved, we do weekly meetings. They are in an EU friendly time zone, and so we'd love to have you join us. Check the Argo project calendar for those meetings, and of course, join us in Slack. And we'll be in the project pavilion. Feel free to come tell us what you love, what you hate, what you'd like to have in the project. Thank you so much.