 Hello. Hello. Hello. Hello. Let's give people come in to join you want to wait too long because it seems you have a really active gender today. As always. So yeah, otherwise for today we have three main topics update from the operator working group, especially on the white paper around operators. I familiarize reserve once not for the github's working group in case you want to share something obviously there's the voting that's going on that you posted on the mailing list. And then we have the our group project update presentation for for today. I think we should be fine. I would like to give you some advice, given that 20 minutes. Just want to have people more time to join. Yeah, while we're waiting here if this is your first time ever joining and you want to quickly use yourself to do so while we're waiting for others to join you. Five minutes after know that some people are new here that like to give them the opportunity to just say hello to the rest. This is my first time going to one of these meetings. My name is Matt Clark. I'm a senior engineer in Spotify. In the deployments team. So we manage all our deployments infrastructure tools and I work at Red Hat in the open shoot github's team and we use our CD open source project and excited to be here. Hi, I'm Regina. I'm I work at Red Hat also with DeWon to we use our go CD so here to watch their pitch. So thanks. Nice to be here. Hi, I'm John Pippin. I also work at Red Hat on the github's project. And yeah, I'm glad to be here as well. All right, it's five minutes past the hour so let's get started here. First up. That's a quick update from the operator working group. I think you have something exciting news. Okay, yes. So let's start. Okay, so can anybody hear me? Hopefully yes. I'm perfect. So yes, we have exciting news. So we are about to to get our first draft done. So currently the last pull requests are getting into our repository we are currently reviewing everything and yes. What did we want to achieve with our with our white paper so the reader should get an idea what an operator is. We wanted to find use cases for an operator so as an end user. We wanted to describe what an operator could do for an end user so which tasks couldn't operate the field and yes, how how could he be supported by this, but also for a developer which things could I provide with an operator so which capabilities couldn't operate the have and yes, to get and to get really an idea what an operator can provide for for anyone. We also wanted to create some awareness for the security of operators so there were such things which we are already defined by the by the security working, especially interest group in the white paper. But we also tried to describe what what wouldn't operate. What should what what measures could and couldn't develop an operator take what should he mind off when he writes an operator and also what can I as a user check to see if if a possible if an operator is secure enough for me or what should I which I should I take care of. Additionally, we wanted we are we wanted to get an idea which possibilities and capabilities an operator could have. We wanted to identify some best practices there were lots of white papers for this and so on. We wanted to describe something and give some examples for that. We also tried to get an overview about some some framework so we reached out to the different communities and asked them to write to write a description of the of the framework. And last but not least we wanted to give the reader additional additional information where where he can find further reading about operators. So how will this will a table of content look like. So we'll have an executive summary. Not not really surprising, which will be finished after the after the comment period. We have some foundation topics so we described what an operator is how a design how the design pattern, not only for cubanitas control operators could look like. And we also described the design pattern on the on an example of cubanitas control. Then we described some capabilities so there were some capabilities which are pretty obvious such as installing and upgrading in some points. We have such things as auto remediation and what what you can think of, but we didn't want to use the capability model which is sorry the the maturity model which is currently more or less the standard for this. We wanted to get more in a capability based way to not say that an operator, which has a kind of a capability is more mature than another one, because this must not be the case. Then we described some some the security and risks as I said before. In this place. I want to thank the security if someone is there because they wrote it afterwards we described some kind of operator framework so currently I think we have to keep building we have the operator framework we have to meet the controller. And I think we have kind of cop there. So, if someone knows someone from another from another operator project, please. Everyone's, everyone is invited to describe the operator framework there. Yes, we tried to add some use cases, such as we had, we had, we had one use case for gtops, for example, because this could also be a task of an operator. But we also have a simple use case on top of the of the Prometheus operator. And we're all we're also trying to find some additional use cases until the final publishing. We define some best practices, but we also get this from the from the current literal literature. And at least last but not least we summarized up and yes, this was it more or less so we had some related work because there is a lot of further reading about operators. And last but not least we have to country, we, we spent a section for the contributors so that everybody gets the credit he deserves. Yes, but now it's your turn so currently after all pull requests are there and accepted, which will be most probably tomorrow. We will open one PR with a with a really large document which will include all of the, all of the sections. And then we hope that everyone of you read this document. You have some comments suggestions or something which is not really in the document at the moment. Feel free to open up PR make comments or suggest something on the on this pull request. If there's something to change rule coordinate this with our original authors and if if this are really really simple changes will make the changes by ourselves. The color this review phase will end on the first April and this is no joke. So, yes, and after after this color review, we will write the executive summary around this or round this up and try to get this published. So, yes, this was our update. Are there any questions comments and so on from your side. And send it out to the mailing list once you've done the merging. Yes, so we will do that we will send it out in the mailing list we will send it out on slag on Twitter and wherever so we want to get as many comments as possible from as many people as possible. And just for confusion is you're merging it into one document meaning you're leaving it on GitHub. We will do this on GitHub is looking forward to it so maybe something to my audience to share. And I would now pass over to the gift ops working group. Oh, well that is a hard act to follow I do not have a grand announcement of like principles document being published or anything like that but I will give you sorry the sun just came through my window. I will give you an update. We have been busy nonetheless. So, one of the main things that we're working on one of the first things we're working on in the get ups working group is the get ups principles document. This is in the past we might have referred to this is the get ups manifesto. That is a bit too. Quite the right words so at the moment reasonably concept of get ups principles. We have moved that for those of you who might not have been paying you know been tracking it very very closely we started out with that in a Google Doc we have moved that over into GitHub. So there's a PR where there's some discussion happening. We are also scheduling some synchronous sessions with the to work on the principles document so there's of course a lot of value and doing things from an asynchronous perspective. There's also you can push things forward more quickly with the synchronous we will of course record those sessions and reflect anything that's done in the synchronous sessions will be reflected back into the get repository for those of you who cannot participate. So that's one of the work streams. Yes. On the calendar because it might be easier for people to. Yeah. Yeah, because calories are like super super full but that might help us across the community there. Yep, making a note. And they are for those of you, you know until we have something in the calendar you can find those things discussed in the slack channel. So, do take a look at the slack channel and you can find out when you can join those things. I do not have at this point, a set of milestones so I cannot tell you I mean we are I can give you an order of magnitude. We are not looking to publish the principles a year from now we're looking to publish them closer to a month from now. And then of course iterate on them so whether it ends up being a month or two months I don't know yet. And we will see about maybe getting a calendar. I'm inspired by what you just did Tomas in describing the schedule for your the white paper. The second work stream that we're working on as a website work stream so to really start to kind of articulate and gather, you know, links and things like that that's been a little bit slow getting going but we do have a number of individuals have volunteered for that work stream. The newer work stream since two weeks ago is that the GitOps working group is going to be putting on a zero day event at KubeCon. The upcoming KubeCon in May I think it is. And that is we're doing a GitOps con. It is being co sponsored by Red Hat and we've worked simply from the mechanics perspective so Red Hat is in fact going to be providing all of the infrastructure for the streaming and you know the platform for putting on the event. And is working together with we've worked on kind of putting together the materials from a marketing perspective and so on. In terms of the event itself that is very much going to be run by the GitOps working group we have about three people have volunteered to help with that. We are putting together a schedule where we are going to be issuing a call for papers I think that's going out today or maybe already did. We'll have about three weeks of allowing folks to provide their submissions to that then we'll have about a week of selecting from those submissions. So you can see that it's very much a community event the selection is going to be done by that work stream that's selecting the talks for that. It's about a four or five hour event including some social time and kind of hallway will do our best to have a bit of a hallway track within that. And then we'll of course publish the schedule and it will be I believe we're not going to be charging anything for this so anybody who wants to participate can sign up through their KubeCon registration. So I don't know if it's already there but they should be showing up as the list of zero day events that you can sign up for. And then finally you mentioned Eloise when we first came on that some of you may have noticed if you're paying attention to the mailing list for the SIG app delivery is that we are in the process of electing co-chairs for the GitOps working group we've been doing all of this by bootstrapping just like any volunteers but we do want people to sign up and say yep, I'm willing to invest the time to keep everything moving forward. To get involved in some of the work streams it doesn't mean that the co-chairs do all of the work. But we do want the co-chairs to have enough domain knowledge to be able to help coordinate the different work streams keep things moving forward and those types of things that the nominations for the co-chairs closes at midnight Friday night. It's 11.59pm Friday night, then we'll have a one week voting period and then we will announce the co-chairs. So that's our update. That is actually a lot going on there it's great so I started to people already brought back on the co-chairs like what you also tried to generally do now more especially at delivery but overall hopefully we also find some end users of people from end user companies obviously to join in as well so maybe strong encourage somebody there to participate. Good point. Obviously it always depends on the people who want to. Yep, yep, that's right. Okay, that's great. That's a lot going on actually. Indeed. And okay then that's all pass over to Argo. You see here. There hopefully that should be coming through there in a second. Give me give me a thumbs up if you see the see my screen. Perfect. Thanks everyone. So hi everyone my name is Henry Plixt. I'm a product manager at Intit. I was going to give a fairly quick update on where we're at with with the graduation that we filed for the PR I think was filed submitted a few weeks ago now. I'm going to give a shout outs to all the contributors and users and vendors that have helped get us to this point. I saw that there were some that joined the call as well so thanks for being here today. And thanks for all the hard work you do for for Argo. So just a argues been around for a while but I wanted to take a minute or so just to give a quick quick overview of where we're at and where we've been so far. So as you probably know, Argo is a set of Kubernetes tools for running and managing jobs and applications. Each of these tools can be run independently. But as these tools mature and we see users have use cases that that that kind of bridge the gaps between them we see more and more users. Picking up more of the project and we're also working on getting them more closely integrated so that the users that do use more than one can get additional benefits of running all these together. So during incubation. There was some discussions on the number of projects in Argo. During incubation, we settled on on these four Argo workflows, our container native workflow engine. Argo CD the declarative getups continuous delivery tool, Argo rollouts, or the kind of progressive progressive delivery, which is commonly used together with Argo CD to do more sophisticated strategy and lastly Argo events. So during incubation, like I said, these these were the four projects that were included in Argo. And there was a decision made during incubation that we shouldn't expand these and now when we're marching towards graduation we're still sticking sticking with with these four four here. Workflow and CD are the ones that I've seen the most growth and contributions will see that a little bit later. And there are also the oldest oldest of the four. So just on the history before I go into more data on on what's happened in the last year. So, Argo was was incubated at a startup called a platix, but two and a half years ago now. And fairly shortly thereafter they were acquired by by into it to build a internal self service cloud native platform for service delivery and for the developer community. And as that platform was being built. There was a need that was realized that we needed some continuous delivery tool and that's how Argo CD was was born. Just a few months after after that black rock who was a fairly long term, a long time work or the workflow user submitted Argo events to the project. And another couple of months later Argo CD rolled out and production it into it. And as we used Argo CD internally. We also came to the realization that we needed some way of doing progressive delivery doing some canary and and blue green testing and and hence Argo rollouts was incubated and launched a few months later. And then in April last year, almost exactly a year ago, we were accepted as incubated in CNCF project. And one of the big mind milestones that has happened since then was the, the formation of an Argo bootstrap committee. And this is the committee of a number of contributors and companies that have helped with Argo and a task with with working with the with the community and making proposals and guiding the governance of the the Argo project. And this is a very active committee meets every week to discuss how to move Argo forward and grow the community. Feel free to jump in anytime if you have any questions. So, so this is a view of the number of GitHub stars not it not necessarily a true representation of the of the adoption but it's, it's at least something to give an idea on on how much the project has grown, grown in the last year so if you look at the data line that's incubation less than a year ago. Argo workflows. Now is is is nearing 8000 stars, they've added 50% stars just in less than a year, and Argo CD has almost doubled the number of stars since incubation in just in just a year. And that was something that was mentioned in incubation as well that CNCF wanted to see CD grow as well since Argo workflow was was the was the main project back then largest project and now a year later we can see that Argo CD is really is really taking off as well so so we have 15,000 stars in the project 3000 forks and looking at the dev stats on CNCF were up to 3800 contributors in total, which just over 900 are are actually contributing code to the project and we have a couple of very active slack channels with a total of 5,000 members that have also seen very good growth in the in the last in the last year. And, and just on Argo CD. We've seen the contributors grow very strongly as well and on on get have we actually now have more contributors on Argo CD than we do one on work with a pretty even, but but Argo CD is seen a large influx of contributors. Very evenly spread across vendors users and individuals it's good to see in a mix of various contributors coming in here as well and we're seeing a strong growth of contributors and members outside of into it. In the last week. There was there was a maintenance meeting and I think that 1212 new members core members were accepted into the project and two promotions and of those 14 new members and two promotion I think there's only one new member one promotion that came from into it so we're seeing a lot of contributors come into the projects from from outside from outside from outside into it. We've also done 350 releases in the project in inception. And that is twice the amount since incubation at incubation I think we're at 147 so in the last year, even though Argo has been around for now two and a half years, we've double the number of releases in the, in the last year so pretty, pretty good release cadence releasing, releasing a lot and releasing fast. Of course, also added a large number of new users. We have over 200 official public references. Now, I think that 250 ish in total 200 unique companies. So we have some around 40 or 50 other companies that have self reported are using more than than one Argo project. And we've seen some of the, some of the new notable ones that we've seen here lately, and Nikki from Japan, who publishes the worst largest business daily and financial times based in London. We've seen new rally consumer logic here from the US, Swiss calm European telecoast electronic arts. And as of yesterday, I think, also have PayPal reporting that they've been rolling out Argo rollouts. So a lot of new users. A lot of various verticals spread across the world so really good, good mix of usage and users across the various projects. But in addition to all the users we've also seen a lot of integrations with Argo as a component where we have projects that have been around for a while like cube flow and SQL flow and seldom using Argo workflows as an orchestration engine underneath. We have cooler, a little more recent, which is a unified interface for for managing workflows or different workflow engines, but also support Argo. And then fairly recently we also have the developer portal platform backstage now also supporting Argo rollouts looking for a progressive delivery in on that platform. And then, in addition to the open source project. There was also an announcement by by red hat a couple of weeks ago about the GitOps agent. Sorry, the GitOps operator that they're releasing that that uses Argo CD so we're excited to get fully supported vendor solution here with Argo as well. And, and on the vendor side, in addition to that we also have a number of vendors that have integrations to either list on the website or integrations with Argo that they support for example, is code fresh. That's taken a, a more active role in the Argo community as well and helping adding contributing it a lot. And then we have more passive, more passive. Like, like VMware and digital ocean that still have Argo integrations documented on there in their official documentation but not necessarily being too involved in the project so so overall it's been a great year. Lots of lots of interest lots of growth, not just in contribution but also in in the usage across across the world. We've also seen a lot of a lot of chatter on on Twitter on Slack. And that's how we know that this a the actual number of users is quite a lot larger than the 200 that that that officially sport because you know that the number of companies that aren't allowed to officially proclaim what what what they're using internally. But we've seen, we've seen users that that aren't listed with companies in the users file to that post on on Twitter, how excited they are about the project we've seen people post about training they're doing meet ups and webinars. And it's also really exciting to see some more local meet ups and local presentation as in just in the last couple of weeks have seen meet ups and presentations in Spanish and Japanese and in Argos it's good to see you know how it's spreading spreading around around the world. But in general there's a lot of just great positivity around Argo and not just Argo itself but also around around get ops. And it seems like the audience is maturing. I can tell that the community and the users are maturing. There are less questions around. What is Argo and what is it get ops people people get it now users get it. There's more real use cases. How do how do I take these. How do I take these components how to take these projects and how do I, how do I apply them in my in my situation to understand the understand what what it is to understand what they want to do to understand where they want to go, and then we're just curious to figure out some best practices on getting there. We also also mentioned the user surveys so in February we ran user service for the Argo projects. And we've got about 120 or so unique responses across the surveys. And though there's a little bit of selection bias of course and since, since these were solicitated from, you know, from, from the current Argo users. The the resulting NPS course came in that 68 and 66, respectively for CD and workflow. So even what with some selection bias those those are some pretty incredible and some incredible NPS NPS data. And, you know, as in my, in my previous life as a vendor even some selection bias and I would be incredibly proud over over those and equally here, you know, this is some pretty impressive numbers that show how excited the users are. And how happy they are with with what has been done by the community so far. And show that was a pretty good mix of experience level and use cases in the community. It's not. It's a good mix of better seasoned veterans and new users, some that have just put Argo in production, some of them have run Argo in production for a long time. Almost 90% of the people that responded are using it in production so it's so it's not that there's a lot of science projects going on here that these are actually users and companies using Argo in production. And like I said earlier, but 25% use more than one Argo project, all already. And what's what's what's almost even more exciting than the NPS scores and the reflection of the NPS score is that almost 50% of the people that responded said that they were willing to to share what they're using Argo for evangelize Argo and do case studies provide quotes or write some blog post to do do do some presentations on Argo and that's another good testament to you know how how how excited the user community is and how confident they are with with with Argo. Maybe I'll maybe I'll pass with you with any questions so far. There's something on any questions on chat. There were a few expressions on chat. No questions. Yeah, no expressions, no questions. Okay, I'll keep going and like I said, feel free to interrupt if you have if you have any questions. So the four projects we have released independently. There's just a timeline of when the releases so far that we've had. We're not in a fixed fixed cadence. We've had a regular been pretty hectic with the 350 releases in total and with three 350 releases from 350 releases from the start of which almost half is from around here. And a very intense release cadence here in the last in the last year but even even so, we haven't had any major releases since incubation so some very excited to announce and somebody might have already seen that that we're aiming to have major releases of Argo workflows, Argo CD, and Argo rollouts here in the next in the next month or so. So we'll get up to the first one that all release of Argo workflows will rev Argo CD to 2.0 and Argo workflows to G3.0. There's enough coming in here Argo workflows as a brand new UI is integration better integration more integration with with with Argo events that frequently used together with Argo workflows. There's more enterprise great functionality like controller high availability, making sure that we reduce the timing in case something happens the controller. And it's the start of the new pod we can just do a hot swap and get up and back up and running faster. And in Argo CD, there's also been a lot of new cool UI work, the log visualization has been rewritten and improved to make sure that it's easy to troubleshoot and figure out what's what's going on with with your deployments. We've also found and fixed a number of security issues in in Argo CD. And there's also now a Argo proge security advisory page page on GitHub where you can go and see you know any and subscribe and see any anything anything that we find anything that gets gets fixed. And then last but not least, getting Argo rollouts to 1.0. I'll show that in a little bit we've started rolling it out internally at into it and we'll do more rollouts at into later this year. But based based on our experiences, based on what we've seen from the community and heard from the users. It's time to get it up to to 1.1.0. So one of the things that we also have done for the graduation is a security review. And we completed two phases with trail of bits, which is a company that CNCF contracts with to do security reviews. So we completed that last week. And then they did basically two different two phases, a threat model, which is more higher level component focused review where they're going to design and architecture actors, and just try and, and see and evaluate if there are any, any issues in the modeling and the architecture of the product. One phase was a, a code review more focused on using static analysis tools and manual review of code to really drill in and see you know what's what's going on and and see what's what potentially could be could be an issue. So the, the threat model found 22 issues, ranging from informal to high, and the code review found 35 issues from informal to medium, which, given the size of the project is a really good result. Most of the issues are low or informational meaning that there are things that we just need to document something to report, maybe maybe switch to I think there's one, for example, those were using it. And read his version that was a couple of versions old so just fairly small, fairly small things. The, the, the really good news is there were no critical issues found which is the graduation criteria to meet, but even so, a number of these issues are already being triaged some of them have already been fixed even. So we're charging and prioritizing this to, to, to get as many as possible these fixed here quickly and include in the, in the upcoming releases, and even the ones that are. That's fun attending was this done across all major project so for roll out CD workflows and events. Yes, this is cross. Yes, so this is across all of our goes all for I rolled them up instead of breaking the mind when we have the report and will share that as part of the graduation process, but this is this is an aggregation across all four. And even so for for the medium and high issues that were found. The vast majority of these were also rated with a high difficulty, which means that even, even if there's a medium or high impact, the ability to, to actually exploit these would be very tricky and very hard. And another thing that we've been working on to, to, to make the project easy to use and more polished is a new website design and contact that content. So a shout out to to code fresh that has helped a lot in getting this going. So currently, the, the four projects have slightly different website, the information is, is, is scattered slightly differently. And they have slightly varying degree of mature of the content. So we're building a new website that's going to be more streamlined consolidating coordinate that the information across the project streamline documentation, making sure there are getting started guides that that that are similar across the project. People can get started, not just with a single one, but get started with all seems to see that as more, more common use case. And also making it a little bit more polished, making sure that we take advantage of, of all the users that are excited to provide quotes and case studies, and data on the usage and make it more of a, a product and then then project feel here and and making sure that people can find the information they need quickly, no matter which part project it is, and getting information on other, other use cases, other users using it, and make sure that that, you know, everything looks like like a coherent coherent project across all the four, the four sub projects. And I think I've written here in the end here I just wanted to highlight a bit into it is still one. It's not the largest users of of and we've grown quite a lot since incubation, as you can see here the number of applications that we have deployed it into it was about 4000 at incubation and now we're, we're over 11,000 almost tripled the number of applications. And we now have 5000 developers onboarded on to onto this platform.