Kubernetes SIG Release, 15 Feb 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting (1.27) for 20230215

Description

Kubernetes Release Team Meeting (1.27) for 20230215

A

I go ahead and start recording.

A

All right, sweet good morning or good afternoon, wherever you may be today, welcome to week six of the kubernetes version 1.27 release cycle I will be your host cat Cosgrove uh before we get started. I do need to remind everybody that, as this is a kubernetes release team meeting, it does fall under the purview of the kubernetes code of conduct, which pretty much just boils down to be nice to everybody else.

A

uh Also a reminder this is being recorded and it is going to be posted on YouTube. So keep that in mind when you're talking there will be time at the end afterwards. If there's anything, you want to talk about that. It's a little bit too sensitive for the recording. So uh let's get started with the team updates because it doesn't look like we have any open discussion items added in here. So first up enhancements with Nina.

B

Yep, so uh enhancement status is green. um Last Thursday was the enhancement freeze. uh We have 78 attract enhancements, uh 33.

C

B

30 beta 15, stable and zero deprecations track does enhancements nice.

A

Spicy all right uh up next CI signal Grace.

A

I know you're here, but we cannot hear you.

A

uh Grace, you are muted in Zoom.

A

Can you guys hear me yep now we can hey there all.

C

Right, um we are currently yellow with um one feeling: it's like flaky master and forming zero feeling inside flaky in master blocking.

C

um Some of these have been been ran yet since they fail slash, flake and then uh some of these, the Sig has ACT them, but doesn't have the bandwidth to work on them. Yet um so that's why I kind of have them at yellow for now, because we don't have a way to resolve them. Yet.

A

Gotcha, okay, still it's uh early enough that that doesn't feel unsafe. So um any questions for CI signal on that nope, cool, moving on uh bug, triage.

D

Hi um um um I'm telling me out um so the updates that we have today uh are: we actually updated the GitHub board to include query to include the current Milestone, which is Gates 127. uh We are working on getting the handbook up to date because we have migrated to GitHub project and also everybody in the team. We have started following up on um the steel issues and the other issues and PRS in the Milestone. So overall status is green. Thanks, sweet.

A

Salem so far, uh any questions for bug triage didn't think so not with everything. Green uh next up is Docs, hello,.

E

I'm Richard and uh is uh it says that will start refreshing the dogs Branch more regularly uh soon enough and right now the current status is key. Sweet.

A

And then release notes.

F

Hey everyone uh release notes is green. We have engaged with all the sigs about the major themes and we're uh we've heard back from a handful of them already um later this week, we'll be um creating the website and release notes for the Alpha 2 cut, and that's all we've got.

A

A

Okay, any questions for comms.

A

This is still slow season for comms. So all right, then, we've got release brush Branch management. I. Think cc is our fearless representative. This time.

G

Oh yeah hi, um so release Branch management is growing and we just cut the Alpha 2 um yesterday, obviously case of one of them already know so, um and I'll update the um template to add another step into the radius cut in the future for the attacking the published boot yeah. That's it! Thank you. Okay,.

A

Any questions for release Branch management.

E

A

Then it's our Emeritus advisor James.

H

Hello uh no particular update for me this week. uh I I still have a few to Do's, mostly around uh arranging the musical Shadow survey and gonna hit some stats out and things like that. But no particularly update.

A

Okay, uh then all that's really left is our current leader, uh Xander.

I

Yeah I, don't have any specific updates. um Still like I was mentioned, enhancements, there's been no exception, requests which I, don't think has ever happened in my yeah since 120. So.

I

um And it was a high number of enhancements, so um really awesome, job enhancements team and everyone um yeah. It's uh it's gonna, be a big release. um Yeah! That's that's all for me.

A

Cool well, this has been a quick, clean meetings, green like nearly across the board and easy okay. um We don't have any open items to discuss. um I, don't think anybody from six scalability is here, but they're marked as green. So uh is there anything else? Anyone would like to discuss on the recording.

J

No uh hey uh quick question regarding the register, but uh last time in the call, Ray had brought up a question around making sure that we document the changes related to the deprecation of the kts.gcr.io, so the changes were done seemingly in 125, based on the pull request that I was able to dig up. uh There is a section that you can add in the release. Note called action required that gets pulled up into the release note under the Urgent release, node section urgent release, entry sections.

J

So how do we make sure that that information gets pulled into 127 to make sure that people are aware of the file that it's actually not going to be pushed into the greatest GCR dot? Io anymore? The images I couldn't find a way to do that easily without actually just creating a dummy pull request with the action required entering it.

A

uh Ricky, do you know the answer to that or do we need to uh engage James on answering that one.

F

A

James, do you have any thoughts, or is this something we just need to bring up offline and try to figure out.

H

Probably best to engage offline, um okay I mean your final kind of option, for it is just to to manually edit the generated release, notes right like yeah, that that's always an option. It's not ideal, but it's doable.

J

Or we just created, let me pull request. It basically has an action required which gets screwed up. I guess.

I

I think on my side, I'm personally more concerned with having it mentioned in the release blog than the notes, um because it isn't, it would be good to get into the notes, but it's not necessarily a feature or or it's just that the 127 images are going to be the first images not published to that registry. So I think, like the the core release. Blog is the main place that I want to be sure that we call that out.

I

um Release notes, I think are more of a nice to have that's just my own stance on it.

E

A

uh All right anything else that needs to be discussed on recording.

A

Extra questions, anything all right, I'm gonna go ahead and stop the recording. Then.

A

And start my screen share right.