Kubernetes SIG Release, 9 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SIG Release - Kubernetes Release Team Meeting 20221109

Description

Kubernetes Release Team Meeting 20221109

A

Hey everyone today is November 9 and we are in the week 10 of the 1.26 release meeting. As a reminder, uh this meeting follows the kubernetes code of conduct, which means please be nice and excellent to each other.

A

um Everyone who have joined, please feel free to uh feel free to add your service participants um in the document and let me paste the link uh yep. Thank you, Leo for placing the link again um feel free to add your names there.

A

um There is nothing in the open discussion uh again. We will have our second retrospective at the end of the release cycle. So if you have any feedbacks or anything you want to discuss um from the release cycle, please feel free to add your topics in the 1.26 retrospective document, which is linked in the meeting agenda document with that. um First of all, congratulations to everyone on the code freeze today.

A

Thank you. Everyone for working really hard. Thank you um any anything. Anyone wants to discuss on the open discussion, not we can move to the role updates.

B

Hello, everyone announcements team here, uh as we have the code phrase now, in effect, uh we had a call today uh in the morning about the code freeze where we update. We have updated and followed up to the kep authors. uh Currently we have received six exception requests out of which around three are approved and the rest are waiting for approval or decline.

B

um So that's the status all over it.

A

Thanks, thank you. Anyone have any donations for enhancements.

A

Also, uh the discussion about the exception request is happening in Sig release so feel free to jump in there and add your feedback cool. uh Thank you other. Let's move to CI signal with Maya.

C

Hello, everyone, so our current status is yellow. uh We have uh on Master blocking. We have one failing and four flaky on Master informing. We have three failing tests and seven flaky and uh regarding the failing test, we have updated to the respective six uh as we have released cut on November 10th. That is tomorrow and corresponding folks are working on it. So, yes, that's all from the CI signal. Thank you.

A

um Thanks Mia and so just to add a I believe I I just checked the slack thread uh for the master, blocking failing test that PR is merged and the test would still be failing, because the version marker for 1.25 is yet not created. So somebody need to push something on the release: 1.25 Branch, to actually create that version marker, but yeah. We hope to see that failing test fix in some time. Thank you, Mia. Any questions for CI signal.

D

No, not really um I think we have one um release blocking issue, but this is maybe something for bug triage in general, I. Think right now we have so every day we see like new flakes or new failings, so hopefully, maybe next week we can smooth things a little bit and get a little bit more calm. After all, the new features are merged in. So this is kind of to be expected that we have a little bit of noise right now. I would say.

E

And I think also um can I ask a question um that hi this is CeCe from uh Branch management team um in this current release. So I'm just wondering if the current failure test in master blocking will block tomorrow's beta their record, or we will have a further notification like early tomorrow.

D

I think this is something that we need to ask if, uh like on the issue itself, if that's that's blocking so I, don't know yeah.

E

um Because normally we will treat it any failure in master blocking as a blocker issue.

F

E

The yeah for another release card so um I'll follow up on that. Maybe later after this meeting. Thank you.

G

Yeah and also like, we will confirm this to respective sake and we will update that and tomorrow's go or no go signal. Thank.

E

You for confirming.

A

Thanks: everyone: um okay: uh let's move to buckwheats with Hussein.

H

Hussein's not able to make the call today um so this morning, when I looked this I thought I was saying, had updated and we had zero on on release blocking issues, but it does look like there's two. According to that query, so I'll, along with the rest of the bug, triage team, dig into that today and see see what we need to do there. I can ask the same and um try to get some more information there and yeah.

A

Thank you. Thank you, Xander. Thank you. I.

D

Think one of one of the release blocking issues is already kind of on its way to get resolved so.

F

D

Least, there's a lot of traffic, not sure about the other one. So I just saw one for now.

A

Thank you uh any other questions for Bob triage.

A

uh Let's move ahead with dogs Carolina.

I

uh This is Jacqueline giving the update for docs. We created a PR to update the dev 1.26 Branch, with main also have a PR open with the official release docs, which will only be merged once the one two two six is released, then we have already added all the play: placehold holder, PR messages on all the caps and I've added some insights there. As you can see, we are awaiting a number of PRS, so we encourage folks to open PRS or at least have the placeholder PRS open.

I

uh We are also approaching the deadline for opening these placeholder PRS. That is this week week. 10, so hopefully um folks will address that and week 11 will be the deadline for having your docs.

I

um Your dog PR's, be in already for review. State and Carol also opened a discussion uh to formalize the release strategy with the doc localization I've added a link there, so um the docs localization owners can chime in to that discussion.

I

Those are updates.

A

um Thanks Jackie, this is hard work. Thank you for the updates. um Anyone have any um questions comments with talks.

A

Cool, uh let's move ahead with release, notes, uh Rodolfo.

J

Yeah hi, hey our current status is green. We are working on four requests for release, notes for Alpha agree produced last week and we faced an error running the current tool, but we are submitting an issue to fix this.

J

Also, we are reaching out the different six for collecting major teams at the GitHub discussion there, and also this week we will be painting our beta0 release in order to start working on release. Notes for that.

A

Thanks for the updates, any questions comments for release note.

A

Cool, uh let's move it with com stream, uh Federal.

F

A

F

um The status is green, I hope we obviously I've passed the deadline for the opt-in and we had around 20 opt-in requests to my last updates from the after the freeze. This dropped to about 10 uh because the rest was removed from these Milestones. So that's the working number that we have uh for the next stage, which is having the drafts, which we we are actively going to start working on somewhere around this week.

F

um We've also had a discussion with with others and.

F

Cycle applications block, um we have a collection of the different deprecations and removals and major changes that I I had shared before on hack MD, um and um we ended up following up the previous decision of not having it by saying that by thinking that it would perhaps even in its current state with some updates. It's um it's. It's a good idea to to have it and we have to attentively moved deadline from the 10th of November to the 17th of November, which was an internal deadline anyway.

F

So we're working on on that applet of the mid-cycle applications block. And finally, as Valdosta says, we are also tracking and keeping an eye on the major teams discussion, um because, though that would be instrumental to the fine release. One and that's it.

A

Thanks so much Frederico, thank you for doing well uh any questions. Comments for comstream.

A

Good uh been required with release Branch management with CC.

E

Hi um this is um we currently the with the code. Phrasing effect yesterday, thanks for number one to create the pr, and currently the uh the code base is phrased from blocking all the new coding, and we are currently ready for the beta Network happening tomorrow.

E

But then uh we forgot there is a failure in master blocking I was confirming, if, um because seems like, the fix will pending until some fixing the earlier release got merged, so um I'm just confirming, if that will be a release, cut, blocker or not, and I will follow up later today as well. Thank you.

A

um Thanks CG, again I believe uh CI segmenting will up follow up with you yeah. uh Thank you. Any questions uh for release. Branch management.

A

Cool uh then we move ahead with our Emeritus advisor uh naborum. If you're undercon.

D

I think he's not on the call.

A

um When do you do.

D

um Right so so as as we all aware, because we said it multiple times,.

C

D

Had a code freeze yesterday, so everything went, kind of smooth, I would say: I, don't know no big problems.

D

um We received a couple of exception requests we also um so that with the enhancements team, so three received uh three accepted in three under review. Hopefully we can finish the review today and they opted or they requested an extension until end of the week. So, let's see um if the folks in the respective six are plus one on that, if if they are or if they are like any concerns, but besides stats, everything is fine. I mean right.

D

Now it's a little bit un like uncertain times, I would say because of code freeze you will see like which changes maybe not make it into the release.

D

So probably next week, as I said, things will hopefully be a little bit uh smoother and we will not have as many problems on CS signal on the Cs signal, dashboards and so on.

D

um Next week on Monday we will also start the another meeting.

D

um I think the invite is already sent out and I will also start um on. Tuesday and Thursday is slack threat. So if they're like any new updates between like Monday and Tuesday, then you can drop it as a note into the stack thread. So we will, for this release, not have um form. You know four meetings, five meetings. We would just have the three meetings on Monday, Wednesday and Friday, and use stack threats on Tuesday and Thursday, so I think that's a little bit more effective.

D

We don't have to jump on call every day and um that's it.

A

Thanks Leo, uh thank you for the updates. uh Anyone have any questions for our release, lead.

A

uh So I see uh we have an update from six scalability. That overall status is green um Alexander. You are on the call.

A

If not, uh then we are at the end of our meeting. uh Anyone want to discuss anything else before we stop the recording, please feel free to talk now.

A

If not, uh then we can take our almost 15 minutes back. uh Thank you, everyone for joining meeting. Thank you. I'll! Stop the recording now.