 Hey everyone, my name is Steven Augustus. I'm head of open source at Cisco. I'm also one of the kubernetes project Leads for SIG release today. We're going to be chatting with you about Kubernetes project updates. What are our favorite projects in the world, right? So if you have ever joined me for a presentation You know that I value deeply the human component of open source projects and And and kubernetes is is a project that is near and dear to my heart So in every one of these presentations, I always want to talk about the human component a little bit now If you have a few have read kubernetes press in the past You will know that a lot of a lot of our spokespeople if you will like to talk about project maturity and and kubernetes becoming boring And I think we're I think we're moving steadily towards that point now I'm going to practice a few numbers with you 22 38 34 42 I like that one and 51 So Okay, practice is over. Why did I choose those numbers? So if we look back into the release cycles Going back going back from 117 those are the numbers of Enhancements that were landed for each cycle. So if you're familiar with the project, you know that enhancements are our our designation for features Really an enhancement is meant to you An enhancement is a designation for a set of work that spans across multiple release cycles Right, so it's not it's not easy to encompass The entire scope of a feature in a single cycle often it takes multiple cycles for a feature Our set of features Components to move from alpha to beta to to GA or stable So enhancements is kind of that bucket that we put All of those all of those components are that a set of components that would be Delivered within a release or set of releases now. So again one more time with those numbers 22 for Kubernetes 117 38 for Kubernetes 118 34 for Kubernetes 119 42 for Kubernetes 120 and 51 for Kubernetes 121 Now with those numbers you can kind of see an upward trend, right? We're kind of we're kind of going up into the right roughly, you know with the with the exception of The difference between Kubernetes 118 and 119 We're trending we're trending upwards right and that's that's that's nice to see in terms of enhancement delivery especially with a the number of enhancements going being graduated or deprecated we're looking at like 13 from from Kubernetes 121 now the reason I mention these numbers is it very much so has to do with The evolution of process right and I think that we're we're approaching a point in the in the project where we have we have kind of iterated over Different approaches for several different things and we're starting to find a fit We're starting to find a lot of things that work for us. We're starting to find a lot of different ways in crafting conversations To be more effective to increase the reach of those conversations so the first one if you were hanging out with us for for kube-con and a virtual in 2020 I talked about the release cadence And again the human component of the Kubernetes project now in 119 we slowed down the kubernetes release cadence are we elongated the the one the 119 cycle right that was kind of a special case and following that following that choice this was kind of like the peak of of you know of COVID-19 as well as protests across across the world and We thought that it would would make a lot of sense to give Everyone the time and space that they needed to really Process to be able to do good work So we extended we extended that release cycle after many many discussions now what followed were Were several questions about Would that be the new release cycle is is now that we've extended it now that we've elongated that cycle it effectively moved 2020 from the standard for releases a year down to three releases a year and we got several questions is Three releases a year going to be the new norm So when I chatted with y'all last We said we're gonna wait. We're gonna see we're gonna get lots of feedback from people We're not going to move on this decision Until we feel that we have we have had an opportunity to chat with a bunch of different people and and get their takes and kind of incorporate that feedback into Proposal right so if you the Kubernetes enhancement proposals are Caps as they're affectionately called so the So sig release along with sig architecture and sig testing produced a Proposal for changing the release cadence and we recently landed that proposal During the the 120 or towards the tail end of the 120 release cycle So that means that if you have not heard the news yet that Kubernetes is officially after much discussion moving to a release cycle of three releases for the year so it's roughly 15-week release cycles with some breaks in between some breaks that we try to Try to have considerations around Kubecon cloud native con as well as holidays across the world And and what that allows us to do is to take time to spend spend some effort in areas that That at times can can often be overlooked right areas like like product management product program project management being able to do triage on active on on active issues and PR's being able to bring more contributors to your respective sigs or sub projects and And and give them give them opportunities that may may not have existed in certain areas around triage around the the product program project management and and definitely not to be forgotten the Time to improve tests improve test coverage fix flaky tests have discussions around the proposals the the level of effort that's required and the the amount of commit that sigs are going to to to to have for for the next cycle right so overall I think that We are we're fairly confident in This being a quality of life improvement for everyone who both contributes Contributes to kubernetes as well as those who consume kubernetes. So thank you To everyone who is involved in those discussions. They're incredibly thoughtful discussions We took quite a bit of time to to to ship this because we wanted to make sure we had those discussions So as a result of this this I want to go back to those numbers really quickly, right? So we're looking at 34 42 and 51 right Those are the numbers again for kubernetes 119 the enhancements for 119 for 120 and for 121 So already There is a there's a net gain in terms of in terms of the the enhancements that we're able to deliver with With an extended slightly extended really cycle, right? We're really going from really going from about Three months or quarterly cadence into a roughly four month or 15 week cadence So very happy to see that very excited to see all of the people who have been pushing that forward including the including all of the sig sub project owners enhancements enhancements owners the release team and The wider community for communicating this message out to To downstream consumers as well So as part of as part of some of the process changes that we've been going through in the project we've also we've also started to talk about an opt-in process for the releases and I think the opt-in process has also had a positive effect on the On the amount of enhancements that we're able to deliver for a cycle So what opt-in is is almost as as the name implies for a sig to To sign up for the release cycle essentially they have to tell the release team what they're planning on committing to and that that turns the Release team model for the enhancement sub team of the release team from a kind of a pull model into Pushing information out from the SIGs into the release team. So we've we've seen some success with that we have as a project SIG testing has worked on the removal of Basel Within the Kubernetes Kubernetes repo that is a huge Quality of life improvement for contributors, especially if you consider especially if you consider new contributors or Contributors that are just recently getting engaged with the project having to learn a new framework Essentially for it for doing work You know when you may be used to say using mate files or are you know your handy dandy shell scripts? so I Believe that you know the the year plus of work that it that it took to put together that proposal as well as Execute on it from SIG testing has a huge quality of life improvement for for the project. So hat tip to them The community meetings are back We have been we have changed cadence, you know during during 2020 and moving into 2021 We've brought the community meetings back the community meetings are going to be More lively forum for discussion. There will be discussions around enhancements Discussions around what's happening in the community what what you need to be aware of different ways for you to get involved So I think so I'm very happy to see the community meetings coming back Those are you know, those were one of my ingress points when I was getting started with Kubernetes So I I hope that they are as fulfilling To new contributors and to ongoing contributors as they were to me when I was starting out So with 121 with with 121 with 120 We've had some interesting deprecations happen. So Within previous cycles we deprecated Docker shim and you may be aware that that that led to some Interesting discussions kind of across the community across the internet just to be clear Defrecating Docker shim is not defrecating Docker Docker shim is a component that allows us to interact with containers Within the kubernetes ecosystem it is It is something that is widely discussed on blogs and explained in great detail. Do not worry We have your back there and there is time to make adjustments as needed in and your running clusters or your clusters to be upgraded In addition to the Docker shim deprecation, we also have Pod security policies have been deprecated pod security policies have been in It have been in kubernetes since near inception. It's one of the first features or enhancements introduced into the project and We're moving on we're moving on we have deprecated pod security policies in favor of In favor of some new functionality and we will see So the deprecation window has started during the 120 one cycle And we'll see pod security policies fully deprecated within by 125 now few other very interesting things that have happened kind of around communicating the Steering committee has started to do or we're continuing to do now annual reports for sigs so annual reports. We piloted the annual report program within For working groups and now for 2021. We're reflecting as a community on all the work that our sigs have done Really across the year and we'll continue to do that every year So very excited to see that work happen As you know as as someone who doesn't necessarily get to touch Every sig it's great to be able to go back and read information about all the the great work that other sigs have been doing Asynchronous communications is another thing that has has been huge Especially as we we look at our global situation 121 was the first time that we had that we had a release team lead who was based in apac and that has led to That has led to a lot of rethinking of all the processes that we kind of we have within the release team And I think and I think has has Encouraged discussion around asynchronous communications Kind of across the community. So hat tip to everyone who was involved in improving our processes And making them more Friendly for our global community So we have Wrapping up lots of interesting things that have happened across the last few cycles Structured logging is now in beta pod resource metrics are Are are now active Being able to defend against logging secrets via static analysis So hat tip to sig instrumentation Cron jobs are now stable. Cron jobs have been in beta since 1.8. They're now stable as of 121 IPv4 IPv6 dual stack Support has gone to beta which means it's on by default Graceful node check downs are now in beta Persistent volume health metrics are now in alpha lots of fun things to check out in the community, but Unfortunately, that's all the time we have so when you have a chance check out the annual reports Check out the rundown on may 13th for the 121 release And check out the kubernetes community repo to get more information on how to get involved in kubernetes. Thanks for your time