 Hi, this is Yoho Sapin Bhartiya and today we have with us in our focus release lead of Kubernetes 1.26 Leonard is great to have you on the show. Hello. Thank you for having me. Yeah, first of all talk a bit about this Before we talk about this release talk a bit about what is the the role of Release lead is it like for Kubernetes in general? Is it for a specific release? Talk about that. So the release lead this is a role in the community So it's a voluntarily work you could say so it changes every release cycle so release lead is responsible for Managing orchestrating one release. So in my case 1.26 and next release 1.27 it changes again. So somebody else in the community who has been part of the release team for quite some time steps up to to read the release and Yeah, it's it's Community role. What is the whole procedure of you know folks joining the release team and then you know playing so the ones you have been a Release lead, do you move to different role? You can choose to do something and in the community as you know in the CNCF community, you know fetch water pick wood or Different roles for different, you know, folks are there depending on your interest So the release team in general there's like in like a shadow application So you can join as a shadow. So you have like one One leading the team. So for example the dogs team and you can apply as a shadow So you don't I mean you can you can mess up on everything. You don't need to know anything You can it's like a training program in general. So you basically get like introduced into the Kubernetes community in general So how to work in an open source team and so on and then you basically can switch roles and so on and At the end, you're also kind of good prepared to in like in general to contribute to open source So this is I for example for me in university It's not something that I have not really learned or this is not part of the of the like Like any program or what also so you don't really learn how to contribute to open source So there's like a new world kind of so These kind of programs help to basically just I know get into open source contributing and so on and Also joining some meetups and and so on so you actually touch upon the next question that I was going to ask was that of course when you Contribute to CNCF through, you know, this team you do help the community But what are the benefit for folks, you know, you did type? I just want to go up quickly in detail. It can be your own personal experience What do you folks, you know benefit from being part of the release team? How does it help you so joining the release team and in general is is a great way to meet new people So you have already like this structure So you have the structure of a team and you join and you don't know anybody basically But it's like a big team. It's like 40 people or so and you also join like a special interest group in Q&A So you have like a good way into meeting new people You also have a good for example, if you if you are at coupon or some other conference You have a good opener just in general to talk to other people So I've been part of the release team and then you can talk a bit about contributing to open source So this is one great like Benefit of contributing to release team. You also learn a lot I would say so like how to how this Community actually works together and how to cut those releases and how does Kubernetes manage documentation for example, or how does Kubernetes manage features and everything like this So so you also learn how these break projects work with that and it's also good for your resume and everything so thanks for Talking about it now. Let's talk about communities talk a bit about This release itself, of course the theme is electrifying but from your perspective from the perspective of the community member hand for the larger Ecosystem, what are some of the big themes that are associated with this release? I would say this release does not have like this one major theme. It's like a lot of smaller things smaller like nice nice additions to Kubernetes which measure to some people maybe to some not so much But in general, it's like a it's like 39 features. So it's quite quite a lot of changes. I would say So you cannot really pinpoint like any like this is like a big thing a big major like change But if you you can bundle up those things into for example, like we have like a lot of changes to security We have now for example, like artifact signing which graduates to beta We have now windows privilege containers and also some changes to admission control. We have some changes to metrics so For example that we now have like, I mean most of those things are like also some some of those things are like internal So it matters to for example developers. So in the sense of for example storage, we have like a big initiative to Refactor some some internal code Which is the CSI entry migration which has been now worked on for a couple of releases and we also made some big changes there So these changes does not make so much difference to the end user, but it prepares Kubernetes or the team to basically grow and and continue to implement features and yeah, we have created or written down a release blog post Which talks about all the major themes. So it would be good to dig into or read it and and just See if like any change mentioned on this blog post effects affects you and It also links like further documentation everything. So if you're interested in that if I ask you from because you are lead there for this release Not that in general team, but some, you know, major changes major features, you know, of course changing container images is there removal of, you know, CRI alpha and Some graduation of vSphere, you know to stable So if I ask you from your perspective or the perspective of where you interacted that these are some of course You cannot pick and choose some but some of the major highlights, you know to summarize them. What would that be? I would probably Choose that we so the release team in general So there's like we have the release team and also the release engineering team So there's like two parts basically all under the sick release and the release engineering team has made like some advancements into That we now push the images to a new registry So this is if I have to pick something I would pick the one from from our sick So we we now push the artifacts to new endpoint registry dot KHS dot IO and Before we pushed it to KHS Gcr dot IO Now we have it basically under community control and so on and This is this is a nice nice improvement to get like More autonomy for the community since you mentioned speed I am also curious What are the reasons for picking the team electrifying so this is like every release has a theme It does not need to have like any like crazy meaning So it's it's it's just basically for the release team release lead to to leave a mark basically on on Kubernetes So I chose electrifying which kind of stands for multiple things for one thing. It stands for for Like power consumption in general. So I'm also leading under the CNCF the technical advisory group for environmental sustainability So with the theme electrifying I just want to raise awareness that Kubernetes hosts like huge systems. It's good getting used like everywhere across the industry and with that Kubernetes also consumes a lot of like energy. So which is simply Put just like a problem and maybe that's something that we or that's something that we definitely want to focus on in new releases but electrifying also stands for that we Use a lot of automation tooling this release into creating the release artifacts and everything else and It also stands for that the community itself is just electrifying so it's you can you can basically pick what what you what you like best excellent excellent Can you also talk a bit about? Either some of the depreciations and removals that users should be aware of for the deprecations and removals We also published a blog post For one we now deprecated the CRI API interface To from alpha dot two To V dot one which is basically a change probably most folks So do not really notice that because it's it's already done if you use like certain tools But if you for example now use a container D you need to upgrade to 1.6 So depending basically on the CRI that you are using you need to check if 1.26 Works for you and so you need to refer basically to cryo and any other resource that you use So there's like a bigger Deplication I would say the other ones are a little bit smaller, but they're all like described in good detail I would say on the blog post so this is not Concerned but if I simply ask you that are there any you know issues that People should also be aware of when they move from one release of Kubernetes to you know the next release of Kubernetes also from your perspective how many people goes There are a lot of Kubernetes vendors who offer you know there so also talk about Do you see any friction and how you folks try to remove the friction so that Because what we have seen industry is some folks are running very very older releases and that becomes a problem So as to encourage them to keep up so that there's not a big gap between the latest release versus somebody's rolling Running an unsupported release. So upgrading the the community's version you are running this is This is kind of a problem that folks as you as you said are using like old versions because for example now in the sense for that we publish artifacts to To the registries we don't Updates any I think the last latest version now was 1.22 and Now we only upgrade I think or patch 1.23 releases. So this is the last one. So if they're like any security things Those those things will not get updated to 1.20 or whatever. So it would be good in that sense to upgrade Because we don't we don't have to bend with basically to maintain all those old versions and keep pushing upgrades So this is like highly encouraged usually there's a lot of I mean, there's a lot of folks who are upgrading the clusters So if there's like any problems Usually this is Known so if you have like like any certain setup and you need to upgrade the cluster You're rarely the only one having the problem. So there's like a huge community having also those problems or not problems at all and Yeah, so I would always encourage upgrading the versions obviously not on day one especially not if you if you have like any like very security related or like important workloads, but in general stick with the Cloud public cloud Services for example, so if if they have like a stable release, you can be very certain that this is like and what you should do Leo, thank you so much for taking time out today And of course talk about this reason also the role of release team because people are at times more important than the technology It sells us thank for sharing those aspects as well and how folks can also benefit from joining this team and of course thanks for sharing all the Details about this release and I look forward to talk to you soon again. Thank you. Awesome. Awesome. Thank you. Thank you for having me