Kubernetes SIG Release, 13 Jun 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kuberentes SIG Release (1.28) for 20230613

Description

Kuberentes SIG Release (1.28) for 20230613

A

We everyone welcome to the Tuesday June 13th release meeting. My name is Jeremy and I'll be the host today, a couple folks had some conflicts, so I don't think we're going to have a ton more people show today, but um I've added the agenda into the chat. um Please feel free to add yourself as an attendee for today, if you're in attendance thanks Ray for doing that already, uh we don't have much of an agenda right now.

A

um So hopefully we'll we'll go through this pretty quick. But if anybody wants to add anything or if we have any last minute, topics we'd like to discuss, feel free to add them at the end of the agenda, and hopefully the meeting invite is corrected. Now we just edited it before the meeting started to make sure that we replaced both references to the meeting or to the zoom link, um not just the one that I updated in the past uh before we get started. This meeting is covered by the kubernetes code of conduct.

A

So please be mindful of what you say and we are recording, so this will be available on YouTube later today. All right with that sweet uh with that we'll go ahead and move to our reoccurring topics. If anybody wants to volunteer to take notes, that would be awesome. If not I can do it um first up. uh Do we have any new folks that are attending today? That would like to introduce themselves.

B

Hey I can uh I can go before.

A

B

Video is is uh not correct, but um I. Don't know why it's showing this white background, but anyway uh my name is Mark. Pruitt I am uh with AWS work on the eks team and uh just trying to get more involved in some of the Upstream release stuff. So this is my first first time joining.

A

Awesome welcome.

A

All right, okay, uh we'll move on to our sub project updates and I can kick off this. um We finish the go updates, so we've updated the release branches and the master Branch to the most release. Most recent go patch releases and all of the tooling has been rebuilt and available. So it should be good to go for the patch releases this week, um the last of the Cherry picks and stuff merged in last night. So those should be fine.

A

um We did run into a weird issue that I, don't think has been seen before, where we needed to bump all of the go.sum files, um which required an API approver, which kind of hard to come by right now, because it's summer and people are on break, so we had to have Tim Hawkins thanks Tim, um to approve basically every cherry pick and every uh everything that was in KK that we needed to do.

A

Do we think that it makes sense to document that in the the template for opening a new go issue just to like, as the thing to be aware of so folks, have that as context for next time, because I think it was a surprise for everybody.

C

Yep yeah I think it makes sense. Okay, cool I'll take.

A

C

Actually, it's me, it is like I think only one thing, only ones that this happened, but let's document it, let's provide an example like a link to the pr yeah, and just you know like okay, this Captain this is just able to be already. Did it.

A

Okay sounds good I'll do that after this meeting is done.

A

All right um next up uh patch releases, do we have a release manager volunteer that would like to do them tomorrow.

C

A

It's a week from now.

C

I'm not sure but I thought I think.

A

Let's, let's see.

D

I was gonna, say if it's tomorrow, I can help out. um If it's next week, I can definitely lead it.

A

uh Target date on the website is 14th, which is tomorrow.

C

Okay, yeah and then it's my bed.

A

Okay, Jim: do you wanna, try.

D

To so I've got kind of spotty availability tomorrow. I can definitely help up, but I don't want to put us in a position where my unavailability puts us in a standstill so happy to pair up with somebody on it happy to kick things off kind of play it by ear but yeah.

A

Okay, I can kick it off in the morning uh morning, my time and then we can um tag team that, through the rest of the day, if that sounds good, yep sounds perfect.

D

A

All right cool um that was it from the release: engineering side um Marco. Well, while you're here do you want to give an update on how the OBS stuff went during the last Alpha cut.

C

I can type so yeah. This is the main reason I'm here for today, because I'm working so I would have to jump on Steam. Well, the thing is that OBS sent out look at the release, commit 128.

C

C

uh Bigger problem, and then there are some concerns from seek it's infra about their detection, because there's an issue in case IO about that so before being able to graduate protein, then do a bit more with that. You have to solve those two multiple results: that's going to require help from obsc, but that's also going to be all full McDonald's I am going to be on attention for at least a week, but potentially until I do think so.

C

I, don't know how much time I've attempt to work on this intern because it's not a real location, so yeah, but as soon as the embassy and time today, we had seen and I thought that you can move forward in July and have a free stuff.

A

All right cool, thank you for the update. It was really cool to see that happen with the 128 Alpha 2 cut. It was nice to see things kind of falling into place.

A

Okay, any questions about release engineering, subproject work.

A

Okay, thank you. Marco all right, Next Up release team Grace. Do you want to take it away? Yeah.

E

um Hi folks, we are at 66 enhancement, which is double from last week, which is a signal to me that the prr freezes working um enhancement freezes two days from now on Thursday um we have a little enhancement, freeze parties on the release, team secret release, um calendar yeah. That's it.

A

Awesome any questions for the release team.

A

Everybody always comes in at the last minute, but I think the deadlines do the thing they're supposed to do. You get people to actually commit to things all right, cool I think the only thing on the agenda was uh Grace. You added a topic about speaking at cncf, Toronto Meetup.

E

Yeah, um so uh they reach out speed, I'm gonna talk to them about. You know how you can get started on the release, team and sick release. um That is next Thursday.

A

Cool that's exciting.

A

Do you need any support or anything for that.

E

um Let me complete the presentation first and I might just kind of send it in the sick. Please channel for feedback. Okay,.

A

Sounds good happy to help, however, we can all right if there are no other topics, we'll lend it early. Today, um thanks for thanks for attending mark from uh from AWS uh Mark asked a question in the chat. What was the date and time for your presentation.

E

So it will be in person in Toronto um if you're in Toronto, search up skin set up Toronto Meetup, but um I will also drop the presentation in the second release Channel afterwards,.

E

A

All right we'll end it there. If you have any questions or want to discuss anything else, feel free to reach out on this release. Channel and slack um Mark. If you're interested in any uh any ways to help contribute to release engineering tooling, uh feel free to Ping us there. We can probably find some good issues to start with.

B

Sounds good! Thank you. Yeah.

A

All right thanks, everybody have a great rest of your Tuesday bye.

E