 So welcome to ArgoCon. Finally, if you travel far away, you made it. Made it on time, actually. I was so worried about missing and not being on time here because I came a week earlier. So if you saw my tweets, I'd be here for a week. So my name is Carlos Santana. I'm a solutions architect for AWS. One of the program chairs along with Christian and Dan. I don't see Dan here, but he's around here. They will be taking pictures doing the social media. So if you're a speaker, you will get your money shot by Christian and Dan. So we want to welcome you to ArgoCon. And I'm very surprised that a lot of people choose ArgoCon. There's many good co-located events. So you chose correctly. We have to chip someday, right? So we have to chip to production. With that started, captions and translations are available through the Worldly app. We always do it in KubeCon. You can take a QR code. And as always, we follow the code of conduct of the CNCF. This is the CNCF project. And you can find everything associated with that, including reporting events. Hopefully nothing happens around here. Everybody will be kind to each other. And the next thing is just a recap of what we've been doing with Argo during the year and then almost this year. There's been many seminars and webinars happening. But the last ArgoCon in Chicago was a very successful event. I tried to take pictures of all the fun stuff happening there. Also, a lot of people make a lot of connections there. We can see Dan fighting with the Star Wars lightsaber there. So if you were there, I bet you had a lot of fun. And you're going to have fun also learning in this ArgoCon. And what I want to say is Argo is a community project, CNCF-graduated project. But the important thing is the amazing number of users that are using Argo, the different projects. Argo workflows, Argo events. And what makes special this community is the amount of people that are users and then seeing some of those users becoming maintainers. And then we'll be having some updates today about maintainers. And celebrating you becoming a maintainer or a contributor of Argo starting as a user. Because that's what we see in the community. In terms of Argo, we took some DevStats. And the project has been growing for the last year. It's about 8,000 commits, 14K APR. So these numbers are continually increasing. And this is the third largest project in the CNCF by the number of authors. And with that, we have Alan and Michael do our updates for the Argo project. So I'll leave it to them. Thank you. Hello, my name is Alan Lucas. I'm one of the Argo maintainers. And I'm a software engineer at Pypekit. I'm going to give you some updates on various aspects of Argo, especially workflows, events, and the Helm project. First of all, I'd like to welcome all the new members of the Argo project. All of these people have joined within the last year. And well done to all of them. If you participate in any way, as Carlos said, start off as a user. You start answering questions in Slack. You start doing issues. You start doing pull requests. You too can become a member of the Argo project. There's a QR code in the bottom right-hand corner that links to the URL at the bottom that gives details of what you need to do to do that and the requirements. To become a member is just about participating. And hopefully some of you out there will decide you'd like to embark on this journey. That URL also contains details of how to be promoted within the project to become a maintainer. And here's a list of all the people who've been promoted within the last year. Big thank you to all of them. Special shout out to Terry Wantang, who's become the workflow's lead, and Zach Huller, down there, who's become the rollout's lead. I'm not going to read out everybody else's name. And we've also had a project promoted to become a full member of the Argo ecosystem. Argo Helm was promoted in 2023 to become a full part. Everybody was using Argo Helm. And now it's sort of properly in the ecosystem. And all of the people below have become maintainers. As part of that, all their efforts have gone into making that a successful project. So thank you to all of them as well. Argo Helm has been working on reducing the overheads of the updates it needs to do. So they're using the Renovate project to automate the pull requests for changes to things upstream. So when Argo CD releases a new version, the Helm charts will hopefully follow quite quickly behind that. They've set a target of three business days, and they're currently succeeding on that target. And so the next steps are to introduce more Renovate for things like Dex and Redis, which are used within the charts, and introducing webhooks so that we get an immediate PR for any upstream releases. This frees up the maintainers to do more work on other useful things. Argo events was released. This has got some new event sources, SFTP, and the Gerrit Gitforge system can now provide events into Argo events. And you can trigger email directly out of Argo events now. Some changes to that's Jetstream to allow smaller versions of Jetstream to run or to use a shared Jetstream event bus between instances. And the final thing for that was templates, which now support all sprig functions. Moving on to workflows, the workflows documentation has moved on to read the docs. Argo CD's documentation has been there for a while, and this allows us to get around one of the biggest problems we've had with documentation, which is that we had to refer back to historic versions of workflows, and it made reading the documentation to work out what you needed to do quite hard. So now you've got version documentation. It only goes back as far as version 3.4, which is the oldest maintained version of workflows, and hopefully all current locations that you may have bookmarked will redirect to the new read the docs documentation. Some other improvements that have been merged into the code base, and we've got some pod management fixes that should improve reliability in the event of nodes disappearing. We've got some Chrome workflow improvements that allow you to stop scheduling a Chrome job. If certain criteria are met, perhaps you're getting a lot of failures on a Chrome job. You don't want it to keep scheduling more, and you can also specify multiple Chrome schedules in a single Chrome workflow to allow much more complex scheduling scenarios. There's been a lot of upstream UI co-quality improvements, trying to improve the maintainability and modernizing how that system is working. A lot of PRs listed on the screen, if you want to find out any more details about this. Workflow has also been improving supply chain security, trying to improve our scores on various metrics there. And the development environment now supports code spaces, GitHub code spaces. We've had Dev Container support for a while, but code spaces were being problematic with that. So if you would like to start contributing to workflows, you should be able to spend a GitHub code space to build the code and carry on from there, hopefully. We've got some things in development. We've got a couple of high priority problems. 3.5 merged the archive and live workflows list, and there's been some regressions in performance, particularly there. And that's still not fixed. That's in progress. And there is a situation where the controller will spam a lot of log lines about invalid config maps, which we're hoping to fix with some informers. Some new features. These are not promised. There's no schedule for when these might arrive. Multiple semaphores in a single node. Some metrics enhancements, including open telemetry, and improving the metrics to answer some questions that people want to be able to answer at the current metrics, but can't. Some concurrency control. Things like prone jobs and prone workflows, you can say you forbid multiple instances of them running. You can't do that directly with workflows. You can work around it, but there's no built-in support for that. We'd like to add that. And a fairly perennial problem of making the controller horizontally scalable is at least getting some discussions going around it. And finally, let's talk about the sustainability project. Julie Vogelman's been spearheading a project to get contributions merged quicker. This involves signing up to a bit of a commitment to your time to write PRs. And then the maintainers will, and other people, within the sustainability project will try and get those merged within a quicker time frame than, perhaps otherwise, as a sort of a payback for that. And if you are interested in that, there's a QR code and a URL at the bottom of the screen. I'll hand over to Michael now. All right, thank you, Alan. I'm Michael Crenshaw. I'm at Intuit on our Argo CD team. And I'm also an Argo CD maintainer. And just going to talk about briefly what's going on in the Argo CD and the Argo rollout worlds recently. So with Argo CD, a ton has happened in the last year. So I kind of had to narrow it down to themes. And I think the biggest theme for Argo CD has been scalability in a number of respects. So we're at the point where big companies are using Argo CD in a big, big way. And that comes with, of course, pain points and things that we need to improve about core Argo CD functionality. So some folks have spearheaded the effort by introducing SIG Scalability. It's a group that meets regularly just to talk about the problems we're facing. If you are encountering any performance issues and just want to chat, that's a great place to drop in and let us know what your problems are. And we've done some deep divas. We've got a slack thread with 400 replies on it on one performance issue. So we will go deep if we need to. Out of that, Amazon has done some awesome work doing analyses of how controller sharding works in Argo CD. So horizontal scaling, spinning up multiple pods to do continuous reconciliation. They've developed algorithms that improve how we spread that workload across multiple pods. And you can now opt into different algorithms that will improve performance in your environment. We've got statistics that show how well those work for different setups. Self-service multi-tenancy, apps in any namespace is a system that allows your developers to control some aspects of Argo CD configuration without needing to go to your team, like your DevOps team as a bottleneck. So that has just reached stable maturity in Argo CD. And we've also introduced the ability to self-serve notifications configuration. So if your developers want to set up their own page or duty account, they can do that. And then finally, application set is kind of its own category. There have been way too many performance and scaling improvements there to list, but application set is really matured and I've been very happy with the progress there. So that's Argo CD. We've been scaling it. Argo rollouts, we've been scaling, but kind of in a different way. We're scaling the community. So plug-ins have been a huge part of the drive in the last year. Metrics providers, we've got two plug-ins. Traffic routers, we've got six. One of the most satisfying things about that effort has been the ability to get your contributions in more quickly. Folks have been able to contribute these plug-ins without needing to wait for the core Argo team to review every line of it. And it just helps folks get unblocked and get on to progressive delivery more quickly. Soon, steps themselves will have the ability to be run as plug-ins. So whatever arbitrary activity you need for your organization to happen as part of an Argo rollouts progressive delivery setup, you can implement that yourself and incorporate it into your organization. The second part, second theme for Argo rollouts has been the user experience. There's been an entire refresh of the user interface. And these bullet points are small in words, but they're really big in impact. The new analysis for an UI is brilliant looking. I'm not an Argo rollouts expert. I'm on the CD side, but I can now go into the UI and see exactly how an analysis of the metrics for an application behaved. It's really helped me with, into its developers who come and they say, my CPU utilization was too high. I can pop into that UI and see exactly what the spikes look like and direct the users to help overcome that issue for themselves. So this slide absolutely blows me away. I love to get the statistic. It is, how many contributions are we getting that aren't made by maintainers? The number of maintainer contributions just kind of slowly ticks up over time. That's not what we've seen with non-mainteners. This is folks adding issues, commenting on issues, opening PRs. It's gone 5x in the last year and Argo CD 20x in Argo rollouts, which just shows how many people are really starting to dive in. You've got Argo installed. This is reflective of how many people have it installed and they're finding ways to push it to its limits and come to us and ask for new features and improvements and fixes. So thank you all for these numbers. This has been absolutely amazing in the last year. And then finally, with that explosion in growth and folks contributing who aren't currently maintainers, we have to scale how we maintain these projects. And we've made major improvements. We now have what we're calling scoped approvers, which means if you just want to contribute docks changes or just CI changes, that's sort of your wheelhouse. We have the ability to move you up the ladder in the Argo Proj governance and get you access to actually merge PRs and get things unblocked. So if you're interested in it being a maintainer, it's become significantly easier in the last year. That's allowed people who don't necessarily want to write code to become maintainers. This coming year, we plan to make a more robust system for folks who aren't writing PRs to contribute to Argo Proj as well. So look out for that. And finally, we want you all to be contributors. If you're sitting in this room, if you're excited about Argo, you are qualified to be an Argo contributor. Talk to us, open the QR codes, pointing to our membership documentation, and just get involved. That's it for me. That's it. Back to Carlos. I was going to add something around this and since we have time. Who's a contributor to Argo? Raise your hand. Have you go through the process of submitting a PR, maintainers and contributors? Raise your hand. This is an exercise. There should be more people here that have contributed to Argo. Raise it. So the idea is for the other folks to see who will have their hand raised. This week, take advantage. Take advantage of those folks and ask them, like, how do I contribute to CNCF? And that's a way that you can accelerate this. Michael said scope approvers, not every CNCF project has this system. So if you want to contribute to CNCF, you can do it through Argo and take advantage of this system where you are concentrated in a piece of an area of Argo and be a maintainer. So that's something innovative that not all CNCF projects are doing. So take advantage of being here this week and just network, right? That's part also of KubeCon. Networking of like, I work on my company, I work on platforms, I work on getups, I work on automation. How can I get involved in open source? How can I contribute to open source? Either testing, opening PRs, opening issues, saying that you're interested in this feature. Some people just put a thumbs up, but if you can write something around the line, it's like, oh, we need this at our company because X, Y and Z, that's important. That's a contribution. Like it gets counted when we do the DevStats, right? In CNCF, we count every activity in GitHub as a contribution. So when you see the numbers, it's not just like a line of code, it's everything involving GitHub activities. And Slack is like insanely good, right? Everybody's there, everybody pitched in to help you out. So you can also help other people. If you are a heavy user of Argo, workflows or CD or rollouts, you can help others. And that's becoming a maintainer, contributor of becoming one community. So with that, we want to thank our sponsors. Diamond Sponsor is Acuity. They have a booth, check them out. Another Diamond Sponsor is Co-Fresh. Also, they have a booth. So all the booths are located on my left side. And we also want to thank our Platinum and Go sponsors, Harness, Red Hat, and Intuit for sponsoring ArgoCon. And with these sponsorships, we're able to run this conference. And the recordings, all the recordings will be available post-conference and that's available through our sponsoring through Cloud Geometry. And for folks, maybe the first time in Argo in KubeCon, we used the sketch system for seeing the schedule. We have two tracks. This room is NO3. We have NO4. So it'll be a dual track ArgoCon. So you can move around on which stocks you want to do. We tried our best to keep sessions that are related together so you don't have to move that much around. So that's the reason that's there. Give us feedback to the program chairs, me, Dan, or Christian. And you can also rate the talks and the slides will be available in the same system. And if you have a mobile phone, there's an app and the schedule, there's two schedules for the co-located event and also for the main event that starts tomorrow. So that's the QR code. Just housekeeping stuff. Launch will be around in this session in front of E and S. I think that's it. And the reception will be in 7.1 downstairs at the end after the last talk of ArgoCon. They say this is a message from KubeCon. They said that there's signs for networking and putting signs on tables. I think that's outside. It's not here, but I saw them out there. And then, that's it, right? We're on time with the new process. So welcome to ArgoCon, let's go.