 Welcome to ArgoCon. Give it a clap. My name is Dan Garfield and... My name is Vojtek Cichol. On behalf of the ArgoCon committee we welcome you. We're really excited to be kicking off the very first ArgoCon EU. Very first time we're doing this. Couple of housekeeping items before we kick off. Obviously we want to thank our sponsors for making this happen. Acuity, Red Hat, Codefresh, Harness, Intuit and Pipe Kit. Make sure guys that you check out their stalls there. There's a lot of Argoswag to grab some chocolate even. So make sure you get there. Argo chocolate, Argo t-shirts, Argo trinkets of all kinds. Obviously this session is being recorded and will be available later along with all the slides. There are two tracks. This room is the Argo CD and rollouts room. And the other one is workflows and events later on also rollouts. So it's a mix but yeah, that's the setup. Hopefully you won't have to be doing too much running back and forth this morning especially. And then lastly, I think it's time to introduce our first speaker. Yeah, without further ado I would like to introduce Hong Wang, acuity CEO and one of the creators of Argo. Give him a warm welcome. Okay, we still have people coming. Alright, to grab a seat. I think there's plenty of seats in front. And we can start. Okay, good morning everyone and welcome to the very first ArgoCon in Europe. And thank you for joining us. And a brief introduction about myself is my name is Hong Wang. And I'm one of the Argo project creators and also the co-founder and the CEO at acuity. And I was part of the initial Argo journey at Aplatics and also also at Intuit. And today I'm representing the whole community to kick off your ArgoCon experience. So I know we have new friends here. So I won't assume everyone know Argo perfectly. So I will give a little bit like history part about what Argo is doing and how we get there. So the overall Argo idea is quite simple. And we believe the Kubernetes is the operating system for cloud. It is like the Linux for single machine. And Argo is to fill the gap and make it easy to adopt Kubernetes. With Kubernetes native solutions. So I believe you could tell the Argo project is very unique among all the CNCR project. So it's made of the four products to solve different problems. And they are independent. I believe we have different audience here like someone is coming from the Argo workflow perspective. They are doing the automation, CI CD, data processing. We also have people love the Argo CD, love the user experience and doing GitOps here. So Argo CD, that's the first one at least there is the most popular GitOps solution. And it helps to manage the life cycle of both the business applications and also the system applications like Istio certificate manager. Basically using Argo CD kind of like manage your whole Kubernetes cluster. So Argo workflow is the Kubernetes native workflow engine. Simply, if you already know about Kubernetes, it's basically the advanced version of the Kubernetes job. But it do way more than just job. And Argo routes is doing the progress delivery including the blue, green and canary patterns. It can also do the experimentation. So in a nutshell, it is an advanced version of the Kubernetes deployment controller. It's kind of like can do the job in replacement of the Kubernetes deployment there also. So Argo events is the last one, but not least one. So it's an event-based dependency manager. How we understand it? It basically helps you to glue the external events with the Kubernetes events. So it can trigger the necessary actions in the Kubernetes native way. So let's look back the history a little bit just trying to help understand. So everything started at a company called Aplatics. So we built the end-to-end DevOps platform on top of the Kubernetes before the customer resource definition era. Basically it was not there yet. So that was Argo workflow 1.0. So if you are curious, go to the Argo workflow repository, switch over the branch to be 1.0, you see our old shitty code. So it was a bit complicated system to maintain because everyone saw like C nowadays, controller is everywhere. You basically leverage the ETCD as your database. Then it kind of solved a lot of the pain in there. So later we were able to redesign and rework the core engine based on the CRD and the system became basically the Argo workflow 2.0. And soon we got acquired by Intuit and Intuit asked us to help them to kick off their Kubernetes journey. So after we joined Intuit, we have the tremendous support from the company to execute on our vision. So not only we have the development resources, but also we have the best possible customer to help us to validate our ideas. Who is basically Intuit itself. So new ideas would turn out to be the new project will add it to the Argo family quickly. We got Argo CD, we got Argo routes and we also getting the Argo events from the BlackRock. And those ideas are not random. So but war based on our own experience to adopt Kubernetes at large scale. So in 2020, we donated the Argo project to CNCF and that basically another chapter started. So sort of numbers speaks for themselves. So with the ever increasing velocity, we were able to release new versions and features in a predictable cadence. And the whole system and also adoption were growing exponentially also. So here's an interesting page and kind of like two years in a row out of the 150 projects on the CNCF. Argo ranked the third in terms of the project velocity. Well, I don't think we can beat Kubernetes and giving we are betting on it to be the Kubernetes native solution. So Kubernetes should always be the number one. And then open telemetry also has a very strong momentum backed up by the observability needs. And I'm pretty happy we are settling on the third place here. So thank you. And in the late 2022, we graduated. And that was the defining moment and also the great recognition of the effort from all the maintainers on the contributors. And that was amazing. So I would admit that it was not an easy journey. And mostly due to the fact is we have four products to graduate. So those four products are quite independent and solving like focus on different areas. So we do have to repeat some process four times. And we made it. I'm very happy we made it. And we got a good celebration at that time. And thank you. And graduation is a milestone and not our destination. So it's a trophy and shared by all the contributors. And our journey continues from here. So five years ago. And when we just be a handful of the people working on the project. I could not imagine one day we have about 10,000 contributors like big or small, like from all over the world. I remember in 2018, we discussed the how to celebrate when we reach the 1000 get up stars for our workflows. And four years later, we have almost like 30,000 now. So it's still accelerating. And it's just like amazing journey. And thank you for the support. And a lot of people here may already be our contributors and thank you for the supporting support to get us here. Okay, so this is just some numbers here. But just don't don't take the number for granted. There's just number is number like many companies have adopted our goal in the production. So in 2021, there's was about like 200 companies self reported them. They are using our goal in the production. And in now it's 476. It's a much bigger. The number is keep growing, but it's really doesn't represent the truth to adoption number. It's basically a trend you can rely on. Since not all the companies will not add themselves to our repository. So I'm pretty sure currently there are thousands of companies are now relying on the Argo in the production now. So I mean, speaking of the success of the project, and I would give a lot of credits to our users and the supporters. So thank you for the feedback and participation in the community to help us to ship the product to be better. It is the best thing I could have from the open source and community to cheer us up and keep us going. I can tell that we are working on day to day in the community. A lot of times getting burned about all so many issues, so many security patches. But the being here see a lot of people showing up supporting us means a lot to us and thank you. So this is something very fresh and I got this message from my colleague Alex recently. And someone from the community sent him this screenshot and the rates and who invented Argo CD. And he must be one of the most lovely person in the world. And the second comment is I don't even use it, but I love it. So that's just like something you got this good vibe in the community. Cool. I want to emphasize one thing. So when we are talking about a much larger adoption across different industries, I'm pretty sure like people are from totally different industries here and there. So we have to stay above and beyond regarding the security practices. So the security audits and reviews are already our general practice. So it's done. But we are also actively participating all the CNCF security related program to improve ourselves to the next level. So one thing we did recently is we participated the security slam North America. And there's a code there. Basically we are the team moved our own goalpost. Basically we try to hold ourselves to be a higher standard. So it's just another reflection of our commitment to the security practice in general. And you can fully trust us with your production environment. Here's my opinion is I know I would consider Argo is reasonably successful at this stage. So what makes Argo tick in the end? So here's my opinion. So I believe we have the best technology in a trust ecosystem. And the people likes the light weighted, flexible and to the point solution. And Argo is doing that. Second, and we have a good diversity. Not to mention we have 10,000 contributors from all over the world. We also have the community made of both end users and vendors. So it's much healthy and strong setup. So keep things going and keep things stable. And the last one list is about effort. And we do committed to work with all the contributors in the community. We are limited resource, but we try our best. We do a lot. Just make sure we fully committed and to make the product to be sustainable here. Okay. You guys already see this page, but I want to call it out. Please get involved with the Argo project. And you can start contributing. You can have the feature request, fixing some issues, do some implementation, do the documentation, or simply help answer questions in the Slack channel. We got a very vibrant Slack channel in the CNC of Slack. And please be there. Secondly, you can be our champion in your company. Use Argo and help your teammates to learn more about Argo. And you can share your Argo experience and good or bad. We appreciate both. And we appreciate all kinds of the feedback to make the product better. So I already mentioned that this is the third time there is a QR code there. So we are doing our survey community survey for this year. So scan it and just participate in the survey and give us the feedback. So I think in the end, I want to thank you for all the Argo Condiment Sponsors, Acuity and Red Hat. And also thank you for the Plantium Sponsors, Codefresh and Harness. And also the Go Sponsor Intune and Pipekit. And thank you for sponsoring the event to make this possible. And please do drop by the Argo kiosk tomorrow in the KubeCon. We have an Argo project booth. And also you guys already know all the Argo vendors to grab your swag. And at last, this is my joke from my last Argo Con. May the think and healthy be with you. Hopefully you get it. All right, thank you.