Kubernetes SIG Release, 30 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Weekly Meeting for 20211130

Description

Kubernetes Release Team Weekly Meeting for 20211130

A

All right, everyone welcome good morning, good afternoon, good evening. um This is the november 30th uh tron meeting of um the kubernetes 123 release team. This is week 15.. um I am your your host today, james liverack. I am one of the release uh lead shadows.

A

um Just before we get started. I can ask everyone to please put themselves down on the attendee list in the meeting notes which I'm showing and there should be a link lying around somewhere. So I'll put that in the chat be useful, um and also can I remind everyone, as this is a kubernetes official meeting to please abide by the cncf code of conduct which boils down to be excellent to each other, all right. Just before we get started on the meeting proper, we have a couple of open discussion items ray.

A

We have a week left.

B

Yeah, so we have one more week exactly until uh 123 is released, uh should should be released by a week from today, tuesday december 7th, so we're almost there.

A

Excellent. Thank you so much ray any comments. Concerns celebrations. One week ago.

A

All right, um the only other thing I see in open discussion items and thank you very much for that right by the way um is uh our standing point about adding things to the least retrospective document. If anyone has any comments, I know in the sig release meeting earlier today there was discussions about branch fast forwarding which I believe has been added to that document as well. So if, if that's something that interests you it's something something to think about um all right, then let's move on to sub project updates.

A

If there are no further comments or questions from anyone, no all right enhancements with grace.

C

Hello, everyone, so enhancement current status is green, we're pretty much at the same place. We were last week nothing new.

A

Good, it's good to hear um any questions for enhancements.

A

Nope all right, thank you. So much grace uh ci signal hoten. I think you're on the call.

D

uh Yeah, I'm in the call so uh compared to yesterday, so nothing has changed. We are still in yellow. uh We have some um yeah more passing in master blocking yeah, so one less flaky um in most informing yeah. We are still you know uh following that. Failing issues, so the the open pr's is still yeah still waiting for the last um um yeah improvers. So I think I'm gonna ping that person from uh sig storage- I I I had to yeah. I had some discussion with him in the past, so I think yeah.

D

We can continue with the topic with him. So in the release cut branch master blocking. So we have one failing and we are following this yeah. The pro request is open yeah, I think yeah. It will take a couple of days till it can be resolved uh in the master informing. We have two failings and uh yeah their github issues open. So I just put new tags on the issues like two yeah prioritize, those uh issues. So that's it uh yeah. Just in case, uh though I think both of them belongs to six storage.

D

I will think yeah the guys again for the girls. That's all from our side.

E

All right uh any questions or comments.

B

Yeah just one, so we do have that one failing job in the sig release, 123 master blocking board, and that is very critical, so the um I I have this on my update, but I'll just state it here that I did add the milestone to that open pr to fix that and um also added the priority critical urgent uh label as well. So hopefully, folks from testing will be able to uh to review that pull request.

B

E

A

All right, um thank you so much for the update any further uh comments for uh for that update.

A

Nope all right, then, thank you. Let us move on to bug triage.

F

Yup, so our status is uh yellow, probably red, because uh we have one release blocking issue which is kubernetes publishing what is broken. uh This was brought up in slack a few hours back and looks like this is related to the commits uh getting missed. uh So that's the issue which is open, and then we also have uh two uh critical urgent issues from yesterday.

F

uh I think those I uh I'll follow up on those and what updates need to be done, uh and then we have uh 13 issues which are getting thought, but the most important one is the other three issues: uh the publishing bot being broken and the go module not getting tagged and popping up fcd client, which would block the release.

F

A

um Thank you for that update. um Do you need any assistance with any of this? Is there anything any of us can do to help.

F

um I would need uh some help with the cave school module not being packed and the fcd bump issue uh I'll, follow up on slack and also on the issue to check. Is there any updates.

A

All right, okay, say: if there's anything we can do do not be afraid to to hollow if needed um any questions or comments on booktubeathon.

B

I think we we talked about um so in the sig release meeting this morning. um Don't know if the, if the go module's not being tagged related, but we did talk about some missing uh tags on um on kkk master. So don't know if if this was is, if it's also caused by the same issue and it's from a missing commit um and also uh the publishing blocks, bot might be sort of discussed as well so um also similar issues.

B

So we we did talk about the in the sig release meeting, um but I'll look into into the go modules and the cd client um issue. It's just. We need confidence, reach any confirmation. I don't see a pull request or any open pull request to bump uh sad clients to 351 and 123..

B

um I did see some comments like this might be in uh after 123.

F

B

Someone asked about that, um so I could, I could think of uh the people on this issue uh if it's going to be targeted for 123.1 instead um good, but I don't see any port requests right now for 123 itself. I did see I'm sorry.

B

um There is a merge, pull request into kk master to bump to about etsy it's two three five one and that's been merged for for a while now so um so might already been. This I'll have to verify if this is already complete for 123.

A

Okay, um I guess we can do some verification and we can circle back to this in tomorrow's meeting.

A

Or right any other comments for for book triage or on any of this.

A

No okay uh vasa. Thank you very much for that update. um Moving on docs with jesse.

G

um Yeah we're we're looking very similar to yesterday. um We've made some progress toward today's doc's friday deadline, um but we're not quite there, um so we're tracking red. um I don't know the specific numbers. The tracking sheet was a little jacked up over the last 18 hours, or so so we just fixed that, so I'm going to walk through and do sort of a line by line check on all the statuses.

G

These numbers are roughly right. So a lot of these are are wedged on final tech lgtms. We don't have any that are that are unreviewed they're, just there's a lot of these in the final kind of final stages, and uh so we're starting to ping ping sigs and make a little bit of noise.

G

There um we're gonna the team's gonna run through another um merge and main back into the integration branch make sure everything looks good there after all of these have been merged in um and then we'll just be sort of in a holding pattern waiting to uh to get to friday.

G

Basically, where we won't be having anything else, merge in, um I think I think that's it so I'll I'll have better data tomorrow, it'll be we'll get this all resolved and uh and updated this afternoon.

A

Okay, um thank you so much jesse. um Anyone have any questions for docs.

A

No all right, thank you very much. um Moving on, we have release notes. Lucas.

H

We're green um we merged and updated uh release, notes draft and we have an open pull request for the major themes.

A

Cool um excellent, thank you so much. uh Anyone have any questions or comments, release, notes.

B

Yeah, um so I made a pull request to cc's um fork and branch. That is, that the pr is from um and just to update the order of it and um it's going into like looking back into the 121 and 122 major themes and how they set the order was more of the deprecations or removals first.

B

Anything important for the release that may not have enhancements like for 122 is the update to the release cadence. So I put like the salsa compliance second after the deprecations and things going to ga after that, after the sauce clients and things going to beta, uh then last the things go into alpha and typically most most most time we don't have out things going, introduces alpha in the major themes, but unless it's really big like um the pod security mission controller, that was one exception.

B

So uh there's there are a few things here in alpha I'll, keep it in there for now and then I'll. You know I'll review so there's another. So there's there's the second pull request: uh tcc's, um fork and branch for that to update uh cc's poor request.

G

A

Cool all right um ray, would you mind finding a link to that pull request and putting him in notes? Yep.

E

A

That right, lovely thank you. um They don't have any further comments or questions for release, notes.

A

Nope all right I'll move on to comms uh mickey.

I

One sec yeah, so we are connecting as a team to um go through the release, blog draft, so we're planning to do that either today or tomorrow, depending on people's availability um and additionally. So that would be the intro section and we're also going through the tech review of all of the future blogs right now and we need to follow up on the comments that are in the blogs.

A

Lovely thank you so much mickey um anyone have any questions, comments or questions.

B

um I'm gonna um update the hackmd to um update the major themes order accordingly to what um what we have and that's in flight and I'll. Try to add a little bit on the theme as well in terms of the intro.

I

Thank you, rick appreciate it.

A

All right, perfect, um anyone have any further comments. Questions.

A

No all right, thank you. So much uh moving on to release branch management, uh veronica.

J

uh Hello, so we're yellow following the status uh closely on the failing and flaking issues. Thank you so much for the hard work, um we're I'm sorry to freak out a little bit uh because we are less than a week left for for the release, but thank you so much everyone for your hard work and just to follow up on the cherry. Picking versus fast forwarding note that that I mentioned yesterday, we started the discussion earlier today at this release meeting there were many many opinions and thoughts.

J

So if you're curious about it check out the notes that are linked in the agenda for this meeting- and I guess that not not to not to just put you on the spotlight, but uh I think that ray might have some more comments about this. So I think that's it for from us today and it's okay. If you don't have comments.

A

Go ahead right have comments.

B

Yeah, um so for for one for the rest of 123, which is a week we're gonna um right now, the process is to cherry pick for any uh prs going into the release. The pr author makes the pr2 kk to the master branch and they would have to cherry pick into the release. 123 branch since that, since the release of 123 branches now uh was now created uh before in 118 and before 118, uh we did fast forwards or or the branch commanders did did daily fast forwards.

B

uh But there's there were some issues with that as well. So it's going to be a discussion in the retro topic, but just for now for the for 123 and with the uh release uh with this um seven days left um the we'll ask the pr author she created to create a cherry pick pr if they don't. um I know there is a script to create to automatically create one. I believe now burn mentioned. There was three um pull requests merged into kk master.

B

That needs to be cherry, picked into the release of what 23 branch, so he is going to take care of that.

A

All right um any further comments or questions for release, branch management.

A

No all right, uh thank you so much for moving on. uh I don't think we have anything from jeremy and I don't see him on the call uh so we'll just move on to release lead ray all.

B

Right um just uh just stop again for jeremy a little bit. I know he would, he would say just to think for rolly to think of uh 124. Think of succession as well- and you know, if you have any uh comments, questions just feel free to reach out to myself and jeremy um all right and to my updates. um We do what's important.

B

What's really important is that that failing job in the sig release 123 uh blocking uh board and there is an open pr on 2k test infra, uh so I've added the 123 milestone, like I mentioned, and also priority critical urgence. Hopefully this gets looked at in the next day or so, but this pull request has been open for, for, I think about a day or right now.

B

um So that's one of the most important things that um that we need to get fixed uh since it is blocking or if it is considered re release blocking. Since it's uh we have a failing test.

B

All right uh milestones for today is the docs for completes um and looks like there's a number that needs tech reviews. So I'm gonna go go and and um ping folks to give tech reviews. For those um also, the feature blocks are ready for review. I believe that is is already complete. I believe the, if not all the all the feature blogs are already at a point to review, if not all than most of them. um This thursday's release notes completes uh so it did see those.

B

um So the release notes completes most since after release, candidates, cuts, uh release, notes can can finish the release, notes and we have the major themes and there's the pr flights um this friday, I'm gonna start a go, no go thread on stick release and so ask the um I'll ask all the role leads to give a go, no go status if we can release on friday and then we're releasing on tuesday. But we want to start that on friday and continue it on monday and tuesday as well.

B

Then tuesday, it's off is release day, so we'll do a final go no-go on tuesday and with tuesday. That's when the branch managers cut the release, we'll make sure the release notes are are in the proper uh in the proper repo and docs will actually do quite a bit to merge in the 123 documentation, changes to the websites and also published the release blog afterwards. The kk masters is thawed, so it's open for 124 and an email or emails will go out to kdev to the community leads into disqus.capexio.

B

um So that's it for me. Any comments or questions.

E

All right, good.

A

As it doesn't sound like it, okay.

B

All right, uh I did pings uh six scalability, uh they haven't added in the results of the of the scalability test, so I'll ping them again to make sure that is. That is up, and we have a status for that for this week.

A

All right, um thank you so much ray uh just before we stop the recording. Did anyone else have any comments, anything to make or bring up at this point.

A

Nope all right, which I will stop recording.