 All right. Good morning. Got a few folks on the line. We'll give it a few minutes or so for everybody to come on in. Aimee say something. I don't know if my audience works here. You are good. You are good. Thanks. We are I'm holding a little bit because well one not everybody's here yet and I kind of need all of you here. So okay so we're three minutes after roughly by my clock and I also see that the app delivery folks are here which is super helpful because we can kick off with them as far as for SIG updates so and I see most of our folks are in so we'll go ahead and get started. Welcome. You have made it to the February 2nd TOC meeting because you are here. You have clearly made it in. Good fun. We'll be talking about our new TOC members coming on in but TOC members present today. Got an update from the various SIGs in here and probably some time for questions so I wanted to go ahead and get things kicked off in here. Elections closed yesterday and very very excited to be able to see these new folks in here and you will get a chance to be able to introduce yourself promises. A big thank you to our outgoing TOC members, Brendan, Matt and Jangly and I'll pass it over to Dave as you are our first official person on the list here. All right I'm actually dropping my kit off at hockey right now so I hope I'm on my phone. I hope I unmuted myself correctly but I'm Dave. I have a TOC for the past few months. I'm an engineer on Spotify's platform team and I've been in various CNCF and CNCF end user things for the past few years. Super. Thank you. Ricardo, I'll pass to you. Ricardo might be stuck on mute. I'll give him a second. Sorry about that. You're great. So I'm pretty happy to join the TOC. I've been working at CERN for quite a while and we've been using CNCF projects for many years now. I've been involved a lot also in the research user group of the CNCF and I've been also participating a lot in cook-cons, clown-made-cons. So I'm looking forward to be able to help. Thank you. Erin, you're next. Erin Boyd. I currently work for Apple and have been part of the TOC since forever so excited to be serving in a more formal position and appreciate all the work Bren and Matt and Zheng have done to lead the way and just happy to be here. Excellent. Cornelia, see you on the line. Go ahead. Hello everyone. Cornelia Davis. I am currently the CTO at Weaveworks. I have been here for about a year. Prior to that I was at Pivotal for seven or eight years, however long that was where I worked both on Cloud Foundry as well as later in the last two or three years that I was there worked on Kubernetes specifically. Kubernetes platform had the great benefit of working as well once I was working together with VMware and once VMware acquired Heptio had a chance to work with many of the engineers over there as well as people like Craig and Joe. So that is kind of my background. So I've been doing app platforms for a long time and have been involved in Kubernetes now for four or five years. More recently this year in particular I've started getting more involved with the app delivery SIG and in particular one of the founding members of the Get Ops working group that's under that umbrella. And I am absolutely over the moon to be able to and honored to be able to serve in this capacity. So thank you very much. Lovely. Thank you. I don't see Harry kicking around in here. So we'll go ahead and move on. If he happens to come on in I will make him introduce himself. So with that I will pass it over to SIG App Delivery. Go ahead. Yeah, hello everyone. So here's a quick update from SIG App Delivery. Let me put my microphone over here. Current project reviews. Flux now also with Flagger. Flagger is currently working on merging with the Flux project or is in process. They requested to move incubation. The due diligence is ongoing. First interviews, first interview has taken place. Some more to come so they should be ready for the TUC to have a look rather sooner than later. On the working groups. So the operator working group which or the operator work in the app delivery which has been around for quite a while had some more momentum and there have been some changes and also some really good work here which you put on a separate slide because it deserves a separate slide this time. GitHub's working group already mentioned Bercanilla. The working group and the project has been formed there. So it's kind of like this lovely existence of being a working group and a sandbox project. The sandbox project for the content created here which has been improved obviously very recently by the TUC. On the model activities the potato had projects with a demo project for deploying cloud native applications which was initially created for a Qube concession has really been growing and there's like lots more contributions from the community that should obviously be Qube Vela. So what it more or less does right now takes is simple one microservice beneath this object that deploys it with well more or less the broader cloud native app delivery ecosystem so you can see a lot of projects obviously from sample manifests to using Helm charts to using Argo to using Flux and so forth and there has been a new projects that were added just pretty recently which is Qube Vela, Customize, NAP and Gimlet and one chart in there. So we see continuous contributions from the community in the next step on that work we're doing there is obviously quite a more complex example based on initial requirements which we had which was stateful workloads obviously multiple services, secret management and so forth. On the CNCF landscape for app delivery there's no update there yet really because we're not that actively working on this also the work was more taking all of those projects and showing people how they can use it as part of the work which we did around Potato Head. On the next slide there is a bit more detail on the app delivery. So again the Operator Working Group Potency Act Delivery we have three new chairs, Jennifer, Omar and Thomas have taken the lead here they have been working on this for quite a while and now we also have a timeline for the Operator Work White Paper. The team also with the Security Working Group who recently did their Security White Paper and took a lot of input from their side. They have a dedicated Slack channel in case you want to get involved with them and there is now by with the SYNC meetings. So the plan is to have something for review by mid of March and then the final version ready by end of April so that it will be more or less done for Yukon Europe. So that's the update from figure delivery. I think there was a question in chat it might be too long for now. Quick question, is Flux and Flagr a sandbox project or is it completely separate right now? It is a separate project but they merged it into Flux and that's also part of the intelligence that we're looking into. Okay and that's gonna they're gonna merge the two projects before they move to incubation or not. That's what they're looking into right now. I think it was ongoing already before. It has been less unusual honestly that the projects that we recently looked into that we have more or less these more or less sets of projects that have individual parts that kind of make it together. So it's also from especially from the Flux side now with Flux we too it makes more sense to have the to have the message as a combined set of projects. Yeah okay Chris posted the sandbox. I think yeah they merged a couple weeks ago or a few weeks ago. Yeah I think it's fair for the project to do to bring those two together and it's part of the due diligence that they did before moving to incubation which I also think is a fair move so that then the combined project can be looked at for incubation. Okay that was the only question in the chat. I don't see anybody else coming off of mute so we'll go ahead and move on. Thank you. Contributor strategy you're up next. Howdy everybody. A few things. First the new contributor site is almost ready for particularly for our new TSC members. What we're doing is existingcontribute.cncf.io is going to become a more sophisticated site where there's one route where if you're looking to contribute it goes to the existing information about how to contribute to each project although that will actually be HTML-ified instead of just dropping you into get. And then the other way we'll actually go to a whole site of information about four project maintainers you know including things about advice on running your project and recruiting contributors and cncf rules and and other things that we gradually build up of which we have some things. We're currently in the process of configuring all the Netlify stuff and also finalizing which pages are ready for publication and which ones still need to be approved by somebody. So and also Carolyn has been out which is why it's not one of the reasons why it's not already done she's been leading that effort. So expect to see that sometime soon. I for governance we're doing final review and copy edit of a sub-projects template. This will give us sort of three standard governance templates for projects. One for projects that have a simple maintainer council setup. One for projects that have an elected steering committee and one that projects that are composed of multiple sub-projects which are the three most common models that we see. Although linkerd is actually introducing experimenting with a new concept for those who didn't see their announcement last week which is they are creating a steering committee made up of end users as a way of bringing more people into the project in leadership positions. So we'll probably we'll be if the linkerd folks can make it we'll be discussing that at 10 a.m at the governance working group meeting. It's an interesting model I look forward to discussing it. The I very early draft this is going to be one of our first requirement advisories. One of the things that have come up with projects recently is the we require projects to have open governance as part of the CNCF requirements but we don't really define open governance. And so as part of contributor strategy we've been trying to add background material and all of the CNCF requirements for graduation levels. And so expect to see there's a link to early draft of that when we finish the draft expect to see that again for full TOC approval because anything that modifies the requirements you all have to approve. The for contributor growth a bunch of documentation in progress recruiting handbook with a lot a lot of questions about how do we recruit contributors and a generic contributor ladder documents in progress because it's something we've had a lot of other requests for. Final thing is so I see contributor strategies had two liaisons to the TOC. Those two liaisons are going to be particularly important in the next season because we are getting the new contribute website online and for things that don't modify the requirements are two sort of TOC liaisons are the ones who do final approval on those. Now one of those approvers is Saad who is still with us and still helping us out a lot but the other one was Matt who is now retiring or at least cycling out of the TOC. So we are looking for a second TOC member who's interested in the work of contributor strategy and willing to help with review and approval of stuff. So if that's you please ping me over chat or Slack or better yet the SIG contributor strategy channel on CNCF Slack. Thanks. I mean other people can also like raise your hand here if you're interested in it. I'm sure we're going to have that problem with like quite a few SIGs so thanks for bringing that up. Any other questions here? Okay we can move on. SIG network. Lee I know you're on the line. SIG network. SIG network. Hooray come on in. Well first of all just Dave and Cornelia Lee awesome awesome. All right so for SIG network we've been well we've been busy with initiatives inside of the service mesh working group. The last three or more four meetings have been really dedicated to initiatives that are going on within that group of which there are a few. Last couple of times we met it much of the discussion and focus has been on Get Nighthawk as a project. We've introduced this project I think a couple of times here. I don't know that we have highlighted that there's some exciting features coming out of Nighthawk as a load generator a sub project of Envoy. One of those is the ability to do adaptive load control which and so we're engaging with a couple of universities to do some studies around load analysis or adaptive load analysis in a distributed way. So we're excited about some of that research we'll see if we don't get to an opportunity to put the CNCF lab to use. The agenda for this upcoming meeting on Thursday centers around service mesh patterns so it's it's a topic within the working group. There have been a little less than 60 patterns identified so patterns being well in some respects best practices if you will about how it is that people can employ and can use service mesh functionality. A lot of functionality there differs across service meshes so the goal is to identify these patterns that are agnostic of the particular service mesh and this coming Thursday there'll be a review of those patterns on high level but with a demo which will include the open application model OAM and meshery and which is a service mesh management plane and so an integration of the two to allow people to take a given pattern as an example and put it to action put it into action. So so that's the upcoming agenda. The other items on the plate is just the public review period or kind of the public comment for ambassador which is proposed for incubation. I think we're you know newt nears I can tell we're currently revolving around naming project project names and and how those relate to maintainers that are involved and so I don't know that I have an update there from from what we see on the on the public thread but so that's sig network. Excellent there's a few questions in chat and as to your point about like the ambassador project yes that is that is tangled up in naming so give that some time but Cornelia if you want to be able to unmute and come ask your questions in here thank you. Yeah so so I love this you know you said it kind of as a side comment about engaging with the university on some research and having that happen underneath the sig umbrella that sounds super exciting to me there's so many elements of that engaging you know younger folks bringing them in you know students things like that tapping into the vast knowledge that's in the universities I wonder if whether there's anything I mean there's a whole story there and I we can't take a ton of time here today but I'd be super interested in hearing about that experience any best practices any tips any guidance how do we make something like that happen and maybe we can take that as a you know as a one-off sometime but if you have any comments to start. Yeah I won't take much time but I'll say that I think implicit to what to your excitement toward the the topic is is probably a number of shared points one of them is that well by their nature universities are kind of akin to the nature of the CNCF and that is to be agnostic or to you know don't really have skin in the game so to speak and so there have been a number of unsolved questions around well in this case around service meshes and microservices and distributed systems and behaviors and really trying to study and understand that so first of all some of those questions are deep and require people to think about it for a while so we've been just makes good for university research and then yeah to be to be all about the the research itself and less about the outcome has been it's been nice we've been a bit we've been intentional about reaching out to a couple of universities either either ones that were physically geographically convenient or some of this has happened in a happenstance way where we end up engaging with oh in the well the LFX or the community bridge program some of the GSoc GSod some of the the internship programs that engage with communities or with not communities with universities through those engagements with those students that's led to discussions with their professors who have or engaged in the particular field of study and so some of that's been a little happenstance I know there's a bit of related to this there's a bit of like there are the CNCF ambassadors program I think Cornelia of which maybe you wear multiple hats in this regard but there's been discussion about campus ambassador program and so that maybe a bridge to explore there interesting yeah there's more in chat from here all the way if you want to be able to talk about your European research project yeah so we what we also do we try to include especially open source related technologies now in the bigger European research project as well with CNCF technologies and actively bring them in which really works pretty fine because an European Union is interested in working more open source and also having more of this engagement in there and interestingly funding is actually pretty good of those projects so is it definitely helpful bringing in different projects and defining contributions and what we also did like the easiest way honestly to engage with universities without what we found and we're doing this now with us we Austrian universities is just offering a basic course on cloud native technologies especially in the math program there is not a lot out there and the universities are super happy doing this so we will our experience was when we were offering teaching people like how to use cloud native technologies so where it's underneath is it's about continuous delivery topics service matches they're super open and allowing to even have these lectures on this and this then usually leads them to for example us supporting a master's thesis and in one case now we are going even to PhDs having like a more agreed curriculum that we could reuse like all of us because we most likely would teach very similar things and would offer our time could be helpful but that's the easiest step into at least I can speak for our local universities here a lot of them don't teach many of the cloud native concepts it's very traditional computer science but they're very open when they get access to these technologies there's lots more in the chat um Chris Ihor I know you've been talking about some things in chat voice yeah and on the curriculum some wonderful ideas yeah that how to maintain a curriculum I think our plan was initially we started with some things internally but our plan was to have this more even open source going forward and if others are doing the same thing I think would be a nice way to collaborate and keep in mind like some of those students depending what you're targeting at you have to start maybe from okay this is a container this is how orchestration works this is how you build and deploy applications it's not like the super high-end stuff necessarily it's really getting them used to the technology that they can then dive deeper into topics that they're interested in and maybe also then reaching out to two different projects whether they have specific research questions just as he pointed out and then having local supporters there but I think it would be a good way to collaborate around these topics yeah and there are some resources available through CNCF um I know yeah Ihor runs the mentorship program here um but in the interest of time I'm happy to chat yeah go ahead yeah I'm happy to chat so if there are any questions for good in mentorship programs and how can be how they can be useful we can we can move this discussion out of the current meeting so we can we can chat on Slack or in some different way anyway as Chris mentioned please check out our mentoring report on the CNCF GitHub so all necessary information is listed there this sounds like it might be a topic for another meeting as well there's a lot in here awesome all right any other questions around SIG network okay we'll move on oh it's like observability um Richie I know that there's probably not much from your side this week because the slide never got updated but happy to pass to you yeah there is a little bit of updates but I didn't get around to updating the slide sorry um so the main update is that there's a lot more uh engagement between Prometheus and open telemetry or not more it's increasing ever increasing um there's also now a Prometheus working group within open telemetry um to um work together on on all the things and I'm I'm having a case of too many tabs Chris there was one more thing the last meeting and yes I know I'm coming here pretty unprepared and I'm sorry for this Richie I'm willing to add two more things for SIG of observability we have the observability one-on-one training type stuff so like blog posts and material is currently being worked on we have a proposal for that uh in part of the observability agenda if people are interested in taking that and also the also talking about open telemetry there is paperwork now for uh incubation proposals so we'll be reviewing that as part of SIG observability for those interested that's pretty much it great okay um we can move on then I don't see any other questions in chat things coming up runtime hey everyone welcome to the new TOC members yeah so um I think not a lot of updates from last time we did actually have two meetings but we're continuing to engage more projects reaching out to more of them and trying to get them to present in our meetings so on the containers and runtime space we have a meeting next Thursday and that's six box it's a project that allows you to run containers like VMs so for people who want to have that VM experience and but but running and run the workloads in containers so we'll see the presentation and sounds like an exciting project and we also have been engaging more of the web assembly runtime projects so there's uh wasmer wasm time and wavm so wasmer uh they are interested in presenting and I've yet to actually hear back from them if they confirm or they are they're going to confirm for uh February 18th uh so wasmer is one of the more popular uh web assembly runtimes you can embed code in or embed in the language uh the the runtime like go or rust or python and you could also uh run them as a standalone using the what they call the wasi interface the web assembly system interface uh and then wasm time is another runtime that is very similar to wasmer and that is part of the bytecode alliance and I think there's some conversations about the bytecode alliance maybe joining the linux foundation but that's not happening yet but that's one of their projects and they also allow you to embed or web assembly in your code and also the support wasi so hopefully we we get them to present soon another web assembly runtime is wavm and we reached out to them and they are written in c++ they're not as popular as the other ones but we still want to you get an overview and engage them swam is another one and they mentioned that they need to get some things together and then they'll be presenting maybe later in the year now in the operating system space we had a presentation from vortail uh and this is basically one of those operating systems or lightweight operating systems that allow you to run containers so kind of like coro s or talos some other projects that presented previously in our meetings and then rest ctl they are presenting sometimes soon they haven't scheduled it yet they responded yesterday they they will they're still interested in in in presenting the project and finally in the ai ops and iot space we did have a presentation from kube flow that's end to end machine learning so from creating your your models and your jupiter notebooks all the way to deploying to a production environment serving that machine learning model and being able to do the inference while serving the model so yeah they presented at our last meeting so pretty exciting and and this is one of the areas of the six so we're trying to get more of the machine learning or mlops type of projects and k3s is another project that we still are talking for them to present they're part of the cncf already so we just want to get more engagement and as far as the run the sake activities so there's a kubecon and you so we're planning to submit a maintainer session so to get more involvement from their community yeah and that's that's all i have for the updates happy to take any questions see if you have any um doesn't look like a question just because i chatter over in chat um but happy to hear from folks oh yeah um there's a question oh wow how do they i know that's a different one i really hope that some of these folks combine projects that's way too early yeah so yeah that's what alina mentioned so there the it's kind of early so hopefully uh they work together because yeah they're doing different they're doing some of the same and you know separately and there's a work or a nonprofit called by code alliance and they're trying to bring in all the projects together so hopefully they can bring in all the communities uh so they all work together and they come up with the same standards i mean they're coming up with the standards but but but hopefully they come up with the same implementation so so there's more of a clear winner um and yeah and this will be helpful for people adopting it and and basically using more for cloud native environments uh and then yeah web assembly is that i mean we had a meeting uh to see meeting a few weeks ago and it's um very similar to what the jbms uh so you create this by code and it can be run in any platform or it can be running on the web uh so so it's very uh transferable and you can uh yeah run it anywhere and so that's one of the things that that it's very attractive um so we'll see where it goes and but but it it seems like uh a lot of people are interested so uh there's another comment that says oh for anyone working on a new uh runtimes our cfd is open okay oh container plumbing oh yeah so there's a conference and that's we'd love to have a speaker on while sometimes okay yeah so for those who wants to somebody from the audience can submit something or we can reach out to some of the members of the sick to submit a proposal there i think there's also an event happening kubecon for web assembly um so if somebody's interested in submitting web assembly talks then it will be great to get more traction in the area yeah and then chris uh actually uh posted the the link on the chat cfd is open cfd is open all right thank you i i don't think we've got anything else so thank you we'll move on thank you sick security jj you did in fact not miss anything go ahead cool cool thanks thanks thanks yeah i mean like i was worried because i woke up late and joined late so um uh sick security i think we've been uh pretty busy the last uh few months and i think uh people have seen white paper come out there's a lot of interest for the white paper and translation efforts have been started for the white paper as you can see there's one chinese translation pr spending and get merged there's also portuguese translation somebody picked up that they wanted to translate that to portuguese so uh that is one effort that's going on membership also be sort of increased to 72 members from 52 different organizations across and pretty active participation uh the other effort that i think got started was uh we spun up uh supply secure supply chain working group there are a few projects that are of interest there i think if anybody who's interested in that i think should join uh given all the breaches and stuff that are happening i think it will be a nice one for everybody to get to know and contribute if if anyone has any time uh there's been a lot of demand for a different time zone uh to join the meeting um it's been there for the last few i mean last six seven months uh that's always been an ask but we just didn't want to move early and create something where there will only be two people attending that meeting so we sort of pushed it out and now officially we launched uh apac friendly uh meeting time uh and if anybody is outside of here wants to join that i think uh there'll be a pretty good way to get engaged with sick security there'll be cross pollination between that meeting and this this and uh we'll probably transfer content over from this to that uh from the us time zone meeting to the apac time meeting we also kick started a serverless security white paper uh that's starting and that's in the works uh it's at the early stages if anybody's interested in contributing to that please reach out to members in the sick security i think they'll get you connected that's mostly about it from my side any questions any thing that i can answer doesn't look like it so thank you thank you yeah we'll move on sick storage is this what you wanted or do you want me to reload it if you could reload it i appreciate it give me a hot minute sorry it's my turn to make last minute changes that's okay you get one free pass this is your one like all you just so you know let's see what it does we'll just run through everybody else's slides first all right much better your turn all right then um so the longhorn project we do need to sync up with sad and review the incubation persistence and go through the dd we also had a new project chamber fs who the that project was one of the first projects we we put through as a sandbox from the sig and now they're looking to move to incubation so that's exciting i'm going to reach out to the project to to ask them to present at the next sequel so we can so we can review the current status and open ebs we have currently ongoing discussions with with the project team and we need to make some decisions there um we have been working on the last two meetings on a project presentation and and a disaster recovery document disaster recovery document is is is particularly exciting we've we've had a new member in the sig rafael s but suoli who has contributed the bulk of the content and we're looking for comments on the disaster recovery document we're we're kind of trying to figure out if we're going to look to publish this as a standalone document or to merge it with the larger the larger white paper we're just exploring different ways of structuring it um but but nevertheless comments very very welcome on that um and we had a presentation of of vineyards which is a project by alibaba which is a fairly innovative use of a distributed shared memory to help with analysis and and various various data management across across communities clusters for very complex datasets so and so it's it's a part it's a bit niche but it's it's a very interesting technology they plan to submit to to the sandbox review process um and finally what i'd like to talk about is um we're we're going through a process to um recruit some additional tech leads mostly because the TOC keeps stealing members of our of our little sig with with saad first and now erin but we have we have two great candidates rafael who i mentioned who who has been the focal point for our disaster recovery document and sheng yang who uh from rancher who has been um contributing to the sig and and working with us for for quite a while too um so i plan to get bios and submit them to the TOC mailing list to start the vote process uh and that's me excellent good fun um any questions in here anything rising okay um of note the next sandbox annual sorry the sandbox review process is going to be on march 23rd um and i have put this over in the public meeting working ducts that everyone knows when that's coming um we'll probably have more conversations about that but that's kind of upcoming pieces in here um and yeah welcome to our new TOC members i i think that's pretty much it for the day any other questions comments things that people wanted to cover okay then i'll let you all go good to see everyone all right thank you hi