Kubernetes SIG Release, 9 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Release Meeting for 20230509

Description

Kubernetes SIG Release Meeting for 20230509

A

B

A

A

Hey everyone welcome to the Tuesday May 9th Sig release weekly meeting. My name is Jeremy and I'll be the host today. um Marco has shared the agenda for us. If you want to add yourself as an attendee, that would be super great and do we have a volunteer to take notes this week.

B

Yeah I can take notes all right. Thanks, Josh get the agenda to come up.

A

That would be great Josh thanks um and before we get started. I just wanted to remind everyone that this meeting is covered by the kubernetes code of conduct, uh which basically boils down to please be excellent to one another, and we are recording this, so it will be available on YouTube. So if you'd like to not be on camera or anything else, just a fair warning that this is recorded and will be on YouTube all right before we uh dump jump into any um sub-project updates or other discussion items we'd like to welcome anybody.

A

That's a new attendee to this meeting. If you'd like to come off, mute and introduce yourself that would be super awesome.

B

Yeah, uh my name is e I work for Microsoft. This is my first meeting.

A

C

uh I guess I can go next. My name is Simi uh I work for Cloudera, uh actually, second, the third time attend, but the first time it got canceled and second time, I joined a little bit late, uh catch the maybe second half of it last week.

C

um The third time yeah today is third time. I. Think I got invitation because I applied for a shadow program. um Yeah. That's why I'm here!

C

D

uh My name is uh my name is and yeah I'm planning to do more. Upstream contribution. I worked in Microsoft at the Azure community service.

B

um By the way, I'm Josh Perkins, perennial Sig release occasional contributor um I actually wanted to interrupt because I'm gonna need somebody else to take notes. Okay, the note stock keeps freezing on me. Okay, I'm, not gonna, be able to keep up yeah.

E

I'm in there and I can help out Josh, okay.

A

Cool and when you have to drop uh Jim I'll I'll, let's do.

B

A

Thanks Josh anybody else.

F

um Hi there, everyone I, am nitesh I work, mostly in the sick country mix area, and this is my first release meeting looking forward to learn and interact with you all.

A

Awesome welcome.

B

A

If anybody else wants to say hello uh feel free or we'll move on to our sub project updates and the first one is release engineering, if you want to say hello, feel free to unmute real quick, um raise your hand, we can call on you otherwise, we'll move on to the release. Engineering update from Marco.

A

Okay Marco floor is yours. Take it away.

G

Thank you so I like to Quick up this. The first one is that go1.34 about that 99 updates are done, so everything basically is jumping so much so we are ready for that side and the next topic is that actually says they're around the corner. Again uh chirping deadline is this Friday and then we have the releases schedule for next Wednesday. This is 17 May. So if you have anything, uh please let us know I have been keeping an eye.

G

Your cherry picks I can requested for some Charities to be provided more details, especially around if you need to share, because some earlier branches or stuff like that. So let's hope that we will figure that out and this to do can be removed because Veronica sent the announcement earlier today. So thanks for taking care of that and I'm not sure if you have anything else from Real Estate generic site.

A

Do you know uh who will be doing the releases.

G

I'm not sure, but we can ask for slack and figure that out. I can take care of that. Okay.

A

We'll start a thread there all right. Any questions for release engineering.

A

Okay, next up is release team, uh Leo Grace said she couldn't be here. Do you want to give us the release team update.

H

Yep sure so the release team today is a deadline.

H

um We close the application, the shadow application um form last week um and since then, we've been so, the the team leads have been looking through the applicants and selecting the applicants, and today we we have the deadline today to make the final um to send out the final emails.

H

So this is getting wrapped up by today. um Grace is working on creating documents and and getting things started. If you like to follow up, we have an issue um which has tons of check check boxes. Basically, it documents the entire release cycle. So, if you're interested in like all those things we need to do or the release lead needs to do, you can follow up there, they're quite a few um things we need to do until next week, so we plan to start the release cycle next week, but everything is on time.

H

So there's no no problems um um so yeah. That's the status.

A

All right, uh one other update our no is going to be the release manager for branch manager for 128. So thanks or no for stepping up to do that, we'll open a PR to add you to the release team docs today.

A

Okay, any questions for the release team, subproject.

A

All right, let's move on to our open discussion items. Marco you've got the first one.

G

Yes, so a quick conflict story for folks that are not involved. So, in the past few weeks, uh secrets and folks from Kilometers work on breaking up a new eks based probable cluster that we want to switch some jobs, that we are running in humanity, JCP cluster and in Google interview, which is something faster.

G

So we actually started doing that and the first batch of jobs he was merged today, so those jobs that are recorded in the pr let's Link in the air, gender and I can also share it here are now running with the new cluster. This includes some of the release blocking jobs as well. So please keep an eye on that. Keep an eye on board, so I will be also taking a look.

G

But if you uh find anything strange, please let us know in single Eck test info channel uh also thanks to Carlos for taking care of many of our projects like telepathy bomb and other stuff. If you find anything else for single list that can be migrated, that is not in the pool of release blocking jobs like for our projects and sub projects. Those jobs can be migrated as well, if they don't depends on any external resources. So if you want to help with that, it is welcome and yeah.

G

That would be it regarding the pr and we're gonna be the change to eks problem cluster.

A

That's super exciting to see, and thanks for all the the work doing, the migration, the eks for profits, I've been following along it's good stuff.

A

Any questions about that topic.

A

Okay, um I had two things that I put on the agenda. uh The first one is I've, updated our annual report PR um little delayed there, but I think I've Incorporated all of the feedback that people had left. So if anybody wants to take a look at that, that would be super useful. um We I think need to merge it as soon as possible.

A

So if you could take a look and review and see if we missed anything or if there's anything that uh looks incorrect, please give a shout out and I'm going to Ping, Sasha and navaroon to review it again because they were the ones that left most of the feedback. I've addressed. Most of that second one I added was uh kubecon. During the contributor Summit there was some discussion about restarting the working group. Lts I opened up issue and sent a mail to kubernetes Dev mailing list.

A

There seems to be a lot of plus ones, not full consensus yet, but I went ahead and I opened a PR to K the kubernetes community, repo to add to the sigs.yaml file and all the other scaffolding it kind of goes along with starting a working group. It also has a draft Charter that I would love to get some feedback and reviews on from folks. If you're interested Sig release will be one of the stakeholder cigs. For that.

A

Okay, any oh Jim, you have your hand up.

E

Yeah just curious I know that we did the um working group for LTS, like probably four or five years ago now and I didn't know if we're involving anybody in from kind of the dismemberment of the original wgs or the working group long-term uh support. The only reason I asked it seemed like we got to a point. I was involved early on with it, as we got to a point where it's like.

E

We all like this idea, but there's not much action to take it's kind of like relying on other cigs and other folks in the community to be interested in caring for that LTS I'm. Sure things are different now, but I didn't know. If there's any Lessons, Learned or like you know, we had wglts before was different now than you know in the past, I guess as long as we're identifying that if.

B

You actually look at uh there's a link to the notes from uh the meeting that we had at the contributor Summit um and a lot of the discussion was about that was about have things changed since we disbanded uh uh wglts in 2019., perfect.

E

What link was that that you're referring to is.

B

It um well, if you look at the pr there's a link to the notes.

E

Go to the 7259 is the document for that issue. That's open, yeah,.

A

Yep and inside of there um the.

A

Let's see if I can find uh which stock it was.

B

Yeah I mean mind you. The number of changes may not be sufficient correct, but things have changed.

A

It's worth it's worth revisiting the topic.

E

100 and I haven't been involved in it nearly close enough to have any sort of opinion, but it's just kind of like hey. This seems like deja vu a little bit. I didn't know if we were already looking at sounds like folks are way ahead of me. So I appreciate that and I'll throw the link in the agenda.

A

Thanks, yeah um and and on the tracking issue, there are plus ones from um a few folks that were involved uh Josh as an example and yeah.

B

We we had, we had all four leads of the old WG actually at the.

C

B

Enough um and we've all endorsed uh reopening the working group, although preferably with someone else's, leads.

A

The pr proposes me and Jordan and Micah housler from AWS, says chairs for the working group.

A

All right, if there are no other questions on that topic, we will go ahead and move on and it looks like. The next topic was from uh natish. Sorry for Miss Bronson um go ahead and come off mutant, bring your topic up.

F

Sure um so I am here to adjust the topic about six Spotlight blog on the sick release that has never been taken in consideration.

F

um According to that, uh the thing is that we actually have a bunch of uh Spotlight blogs and a different variety of six. uh The general process for building a six Spotlight blog is something like uh we generally have certain questions around a certain sick like what are the different ways to get involved within a particular sick and much more think that, and we generally approach uh coaches of that sick to generally ask those questions, because they definitely have a good experience now uh in the last uh Quantum X comms meeting.

F

uh The question was raised about why not? This is a Blog on Sig release, since uh release is very important part of the kubernetes area right. uh One of the major concerns that we uh that was taken consideration was the release cycle changes frequently. So we are not sure who are the actual people uh that are uh staying, constant or whom we can be actually be reaching out to, uh so that uh these people can actually address their queries about the release process.

F

uh Another thing what a spotly Blog does is it actually uh provides a major responsibility on what does Sig actually does. For example, uh what does sync usability do how to get involved with Sig usability and much more questions like that. So I just wanted to know uh what is the correct way.

F

According to the Sig release, uh to have a Blog, Spotlight blog and the sick release, uh should we actually divide that blog into two parts, mentioning what are the different different uh aspects of Sig release, whatever it covers, um or what should be the approach that sick, Quantum, X contributors should actually follow to present a Blog on the six release.

A

So I dropped a link to um our page or our readme file from the Sig release directory in kubernetes community repo I think it depends on what you're trying to cover in the blog Sig release. Has uh you mentioned that it changes from release release like that's one, one sub-project of sigurly Sig release has a set of chairs and a set of technical leads that is consistent um until we rotate chairs and leads, uh but those those folks don't rotate in and out every release. That's consistent like any other Sig would have.

A

The um stick has two sub projects. Currently, one is the release engineering project, which has a set of folks that are contributing doing um you know cutting of branches and maintaining of the release tooling, that we use as part of the release process and then the other subproject is the release team and that's the one that does rotate um through every cycle. So 128, 129 130 will have different release teams and those are folks that are Staffing and running that particular release.

A

I think it makes sense to talk about both aspects if you're covering the Sig, because both Avenue both are Avenues to contribute right like there is definitely an Avenue to contribute to release engineering work on the tooling, become a release. Manager associate become a release, manager, there's a path for that working on the release. Team is another one. That's gotten a lot of focus in the past um Leo. You have your hand up. You want to go ahead and chime in.

H

um Yep so I have a question, um but first I think overall. This is like a interesting or good idea um over the past, like I, mean I. Think since ever we've been talking at conferences and so on, about sick release and also the release team and release engineering, and maybe writing something this into a Blog could be could be very interesting, could be cool. My question would be: is this like a document which needs to be updated? Every uh I don't know half a year or a year?

H

Is this like a or is this a Blog which is basically uh which we don't need to update because then I mean we could also put this, maybe in the readme in a way so where's where's, the blog uh block aspect, that's my question.

F

um Basically, the uh the blog is actually there's no uh particular deadline up, till which the blog should be updated. We actually have a bunch of blogs, and, uh with years passing, we generally update those blogs depending upon uh what major changes have been there.

F

For example, uh like Docker shim, um the change was there, so how did sick dogs actually managed all these things so, depending upon uh what event has been occurring a particular year, we generally uh tend to provide a more specific blog on a particular site such that the reader uh actually reads: uh the latest blog and gets the latest information. Okay, this thing performed this it to actually resolve these many things that were occurring on the way, so there's no uh specific deadline, but uh there are certain sick blocks.

F

Sorry, six portrait blocks that have not been updated over the years and people still generally read it. For example, uh the Sig Spotlight bloggers, usability uh I, don't think so it has been updated since 2021.. So there's no as such deadline, uh but depending on what events actually occur, we can generally uh write a new block like this sick performance, many X2 uh conquer this event.

H

All right sounds good, so it's basically like a very high level overview over the sake. It's not going into detail so probably maybe the in general, the contribution or the letter like what Jeremy mentioned, maybe something we could mention, but probably not like any more details than we could maybe reference to the documentation itself. So it's good.

B

A

Muted Jeremy, if you are talking sorry I, was uh I, said I will take over for notes for Jim, since he was stepping away. um But what uh what do you want to do as next actions? For your blog, it sounds like people think it's a good idea to do.

A

um Generally, you talk to Sid leads for that. uh Is that what you want to do for the for this one, or do you want to focus it on any of the particular sub projects? What's your.

F

um Intent, basically, the uh what we are discussing about is uh having an uh interview with the coaches of a specific six, so I just wanted to know whom I can reach out to from the sick release. That has a specific information about the Sig release, uh questions on how to get involved with the sick release.

F

How did this signalese manage to conquer this event and other other much details, so what I will be creating is uh I'll be creating um a specific docs for the coaches or the people that will be addressing that separate specific questions once they have answered those specific questions, uh we'll be creating a Blog out of it and we'll publish a publishing it on the kubernetes website for the same.

A

Okay, I think your best bet, then, is to use the the link I shared to grab the names of the folks that are chairs and tech leads. uh You could also, as part of that, we can also add in current release, lead, if you want to add in for a little bit of extra depth, but I. Think that'll give you the the folks you're looking for.

A

All right any questions, any more discussion about that topic.

A

A

Okay sounds like we don't have any more about that one. Do we have any other topics we'd like to discuss today, um Marco I, think I had a question for you. We think created a couple of project boards during the the meeting in um and during yeah. Do we want to add those to this agenda to go through because we used to have the project Boardwalk? That was like Board number 23..

A

um Does it make sense to put those here and do a kind of reoccurring triage on those.

G

That's a good idea, but before that we should actually like create initial tickets. We mentioned that if we plan to have uh sessions regarding that, but since everyone was still recovering from cubecon, we didn't follow up with that. This is a pretty good reminder. Maybe we should follow up on that and try to schedule some sessions to uh we have planning I will probably do planning for packages. I can create issues on my own.

G

I will probably do that later this week or beginning of hexic, but we need to figure it out for Designing efforts, I guess for that. We will probably have to wait next week because Carlos and park are on uh silicon or open source, Summit I'm, not sure so after they get back. Maybe we can schedule something and try to take care of the other board as well. Okay,.

A

That sounds good. I will um hang both of them next week, once they're back to uh schedule something.

I

uh Although sander wanted to be involved in in those boards, you know like he offered he volunteered to project manage okay.

A

Okay, I'm just capturing notes. Sorry.

A

Okay, any other questions or discussion about that topic. Before we uh I guess we can call it a day um how about asked? Do we have a list of issues that new folks can pick? um We do have issues that are tagged as good first issues across some of the repos.

A

um There are a number of tooling repos that are open as well. um I, think I, don't know if we have a landing like a documentation of all of the the repos that the Sig owns um should check that uh and verify that, uh but we do have some things that are tagged as good first issue.

A

um If folks are interested, we can probably if we don't have that today, I think we can summarize a list of all of the the sub like the tooling repos, that's going to be the place that most of the issues are going to be open. Since that's where a lot of the work is going to happen,.

G

A

Okay, anything else before we adjourn for today.

A

All right well with that I will adjourn for today. Thanks everybody for attending um Leo says he likes the idea of creating a list of repos the cigarettes, um I'll double check and see. If we have that, if we don't, then uh we'll create one there, we go I'm.

E

Not sure if that's all inclusive or not, but that's the community list like under release engineering cool.

A

Thanks Jim: let's see if uh I think that's pretty accurate. Okay.

E

A

So inside of that, there's a number of tools, yeah that includes the new, um a tester as well. So I think this covers most of what we have so going through those repos and looking for good. First issues is probably a great place to start.

A

Thanks for confirming that Jim I was trying to trying to do that as I was speaking while.

E

You're hosting and taking notes and everything else, yeah, no, no worries.

A

Multitasking, a little too hard at the moment, I'll add that as a link in the docs, though thank you.

A

All right um with that we'll call it a day. Hope everybody has a great rest of your Wednesday Tuesday, Tuesday, yeah, sorry lost track of days. All right have a good one.

G

Thank you, bye-bye.

A

Thank you, bye.