Kubernetes SIG Release, 24 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20211124

Description

Kubernetes Release Team Meeting for 20211124

A

Good morning afternoon and evening, everyone welcome to the 123 release team meeting. This is a week 14 of the release cycle. I'm your host, my name is ray. I am the release lead for 123., I'm just going to share my screen here.

A

Great, please sign in for those who are attending this meeting live. Please sign in to the release uh notes over to the release team meeting notes here then we'll kick it off with the open discussion. I do have a few topics here. I want to thank the release managers uh very much for cutting the release candidates yesterday or last or last night for some of those it might be early this morning and also also for the for creating the branch jobs. That's currently in progress.

A

Do you want to make a note, since tomorrow is a uh us holiday here? uh It is thanksgiving I've canceled, tomorrow's uh release, team meeting, uh but we are still having friday's uh eu apac friendly release team meeting. So that's on friday.

A

So let's move on with the uh team status starting off with enhancements. Don't see this updated. I don't know if anyone's um here from the enhancements team take a look at the chats. I'm sorry the attendees list, anyone here from enhancements that could give an update.

A

All right so going off enhancement, since it's post code freeze tends to be pretty quiet, so they tend to be green I'll fill in the the stats from um I'll ask standard to update the stats here.

A

So let's move on to ci signal with arch.

B

Hello, so for master blocking, we have one less flaky job since yesterday's update and one job was failing and uh hussein posted in the channel and there was a prompt response- and I believe jordan also made a pr. But I still see the test as being like the pr is merged, but I still see it as failing on dashboard. So I think it takes time to update- or there was some discussion that the pr needs to be ported to the some branch which I am, which I do not have. The context for.

A

Yeah, since um the release candidate was cut yesterday and the release, 123 branch was also created. um This the pr to fix this job was. There was also cherry pick pr to the release, 123 branch, and I believe that cherry pick pr is uh is still open, so that still needs to be reviewed and approved. The one two kk uh master has already been merged, though so I don't know how long it takes we'll keep a close eye on on this failing job.

B

Yeah, so basically the fix is out there right, so nothing to worry uh other than that for my strength, forming. We have two more passing jobs as compared to yesterday and one less flaky job. That was it's. The current status is yellow right now, only because of the one master block.

A

Yeah there there's a pretty big thread on the release: sound really ci signal channel about this about the about this failing job and about the fix as well.

A

It looks like it's linked here on the media notes, so that I do have a topic that kind of led from this slack discussion I do have something I did add in the retro as well is- is about fast forward. So I'll talk about that in a little bit any questions or comments for ci signal or arch.

A

All right so we'll keep a close eye on the failing job. Hopefully that will hopefully that pr emerge fixed it all right next up is bug triage with kristoff.

A

And one from the bug, triage team.

A

I do see a few new um critical, urgent issues that were since last time we had a meeting so we'll take a look at those pretty closely. Don't see any critical, urgent or important student prs.

A

And we'll take a look at the issues um and the critical urge, especially the critical origins and also the importance of issues.

A

All right, let's move on with docs, is jesse on.

C

I am you hear me: okay,.

A

C

All right, I'm home, so I don't have all my fancy gear and I'm really back lit sorry, um so we're on the other side of uh ready for review deadline. uh We only have three prs that are in draft, which I think is really great. Given it's a holiday for the us and there's been a lot of last minute stuff, so big props to the team here um everybody's doing a great job.

C

We do have three that all three of those, I think, uh are not uh in danger of missing um being ready for review and time like well ahead of the next deadline, which is november, 30th doc's ready deadline. um So I'm keeping us green for now. I feel, like uh that's a that's a bit of a like, hesitant green, but I it's green. So I'm happy um the again. The integration branch is fine other than that easy cla thing.

C

So if anybody looks at that, that's there's issues for that, there's a whole lot of red stuff, but it's okay. um Other than that. I think.

A

That's us cool yeah, that's great, and that actually is pretty good, really good. At this time we usually have uh more than that up to the day before we are ready to merge for um so that's actually really good great. Thank you very much jessie and the doc scene cool all right. Moving on with release notes.

D

Yep um our status is green and I saw the rc there were card is alive earlier this morning, so I will be working on it today and also for major sim. um I might start to drive to the initial version after today. Yeah that's it.

A

All right any comments or questions for really expense or cece.

A

All right next up is comms with karen.

E

Okay, so we're kind of greenish yellow um the release. Vlog is almost done. There's just a few more sections, probably like three paragraphs that we kind of need to finalize. um We got our last pr for um our last feature. Blog um and now all our future blogs are just kind of waiting for tech review and then the release webinar event page is now up um so I'll link that as well and that again is going to be january 4th um with ray and with xander. So yep.

A

Cool, um do you want to make note on the release blog I'll um I'll, wait when the markdown for the major themes is up and I'll, compare with the major themes in the race blog and um address, if necessary, and probably make some a few revisions, if necessary as well, so I'll make those updates?

A

Thank you all right. Any comments or questions for comms or karen.

A

All right next up is a release. Branch management with neverend.

F

Hey everyone, so we are green. um Today. Today we released the first release candidate for kubernetes 1.223. um It was an adventure.

F

There were some hiccups throughout the process, but thanks to amazing people, we got things done and there was an announcement email like few hours back so right now we're in the process of like finishing some uh post branch cut tasks, so two of them are already done. We have updated the kubekins entry test, image and release branch. Pre-Submits are also merged. Now the only thing which is remaining is uh the milestone: applier update, which should also go go soon.

F

It is already uh reviewed and lgtm, so an april is only left and that's all from us unless uh veronica, if you have anything to add.

G

uh Not really other than it was really an adventure and a true teamwork, as always, but it's great.

A

All right, thank you very much now bring veronica yeah. If you can catch those threads and release management, um you'll see that it was quite an adventure. uh I was watching it until I went to bed last night, then it was still going on this morning. So big. Thank you uh to veronica nabaroon, uh adolfo stephen uh marco, also everyone all the release branch managers. Thank you very much.

A

All right um any comments or questions.

A

All right moving on, I don't see jeremy here jeremy is here. Please speak up nope all right. Moving on um to my updates, sent an email to the committee last night about test. Freeze and docs um also made a note that, since the release, branch was being cut that if there are any uh kkprs um that is targeting the release for 123, they have to have a cherry pick to the release 123 branch as well. um I also need to clarify- I also made on the email to uh about test freeze.

A

I mentioned that you know that we'll monitor test grid and and get um critical, uh failing uh test fix as well. So I need to someone asked someone I'll reply with clarifying questions. I need to clarify that it's gonna be primarily the sig release, master blocking um and we'll be watching sig release master informing, but we do want to get those failing jobs on sig release, master blocking fix or I'll probably state it, and that will get them triaged instead of actually uh fix them uh ourselves. So uh we'll add a reply to that.

A

um Like karen mentioned, the release sub webinars uh is out since I got that email personally, so that's on january 4th, you could click on the link here or um or in the link that karen posted to register. For that also yesterday, we had some major milestones. As you probably know, real excited was cuts with that the release branch uh was created, also the reeves jobs uh or being created right now.

A

I believe that the pr is to open last time I checked that also brings in test freeze as well, so there's no, uh there should not be any new uh tests unless there are critical urgents or that they are fixing some failing tests um to be allowed to be merged into kk, so to wanna did sent that yeah send a note, but an email last night. Also in that email I made a note about the docs should be ready for review and also the docs complete deadline being next week.

A

All right and that's um and the next milestones is this- is next tuesday. The dock should be complete and the feature blog should be ready for review that one's always been a little bit iffy. We get that. We, I know, there's a good number of feature blogs already being reviewed currently, um but some some of the feature blogs are tracked for towards the later of the time frame which we do release release blogs are kind of reviewed a little bit later, so we'll keep an eye out on those as well any comments or questions.

A

All right, unless I checked with six scalability, no change on the scalability test and that's it for the any other comments or questions, if not I'll, stop recording.