Kubernetes SIG Release, 30 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20221130 (1.26)

Description

Kubernetes Release Team Meeting for 20221130 (1.26)

A

Hello: everyone Welcome to the release team meeting today is Wednesday the 30th of November. We are just about a little bit under a week away from the final release: cut um I'm Leo I'm the host for this meeting. This is a community's sick release meeting. So it falls under the cncf code of conduct, which can be summarized to be just excellent to each other and yeah. Let's get started, um we don't have anything on the oh discussion items, so we will jump directly to the enhancements project.

A

Team update with Mark I, see you at some last minute updates.

B

Yeah I don't think that there's any updates from the enhancements team, so everything's still green.

A

Right um one thing: um there was a couple of days ago: we forgot to add one enhancement to the tracking, so maybe we have to check if it's recorded already so this was I. Think I wrote it in the release: enhancements Channel. There is a thread, so perhaps actually we are on 39 38..

A

So maybe we can recheck that but uh I'll.

B

Already checked that yeah I just captured that from a previous date, so it might not be.

A

Updated, though, going right sounds good, sounds good and moving on to CS signal with mija.

C

Hello, everyone, so the current status of CI signal is yellow. uh We have, we don't have any failing jobs on Master blocking and five flaky and on Master informing. uh We uh see currently one failing job and, yes, we have raised up an issue and Sig Windows uh folks are working on it and, yes, we have six flaky ones. So, yes, that's all about CI signal. Thank you.

A

All right, awesome, yeah, I, think Marcus is also in in the meeting so yeah.

B

I'm, taking a look at that I I um I suspect that there was a check-in to the cluster API azure repository where that's used to provision the Clusters based on the test grid data that I saw I started a thread in there. I'll link it back to the thread that is discussing this from the release team too.

A

Awesome yeah, I I just saw that there's no like real, like uh the the issue behind it is, is not like locked into Pro, so you cannot really see it. It's kind of hidden, so I don't know where it is yeah.

B

But based on the logs, the cluster didn't come up. So that's why I want me to believe it's in the cluster, provisioning and I. Don't suspect it's related to any regressions in actual kubernetes kubernetes, but we'll continue to investigate.

A

Yeah my my thinking was because this was moved out of KK that it's probably like on the plug-in side, so nothing really changed on KK. So but okay, great, that you have a look at it.

A

um Any questions to CI signal.

A

Otherwise, let's move on to bug triage with Hussein.

D

Hello, everyone, um so we have quite uh yeah relaxed time, so nothing uh urgent and important from our side. We agree and yeah. So far everything looks good.

A

Awesome, that's great any questions for bug triage.

A

Maybe just one comment from my side: I, don't know if I mentioned I I think we we talked about this in the previous meeting already, but my feeling was like especially in this cycle. The load on Buck triage seemed a little bit low, um so maybe in the Retro we can. We can maybe Hussein yourself some ideas.

A

Yeah, we can maybe help out see a signal or other teams. Sure.

D

Sure we will come back to the point here.

A

Sounds great, then, moving on to docs with a red update from cat.

E

E

um And we still have a few open items, um we do have 32 that have been merged, but two potentially just one: that's in a draft state so that first one has I think two different docs one has been merged.

E

One is still open, I think just trying to get clarity on which one is is what we're looking at and the second one uh has both that are open, um I need and need uh some comments, reviewed, and then uh these ones are are kind of pending LG, TMS and also pending uh changes that have been requested so just kind of barreling. On with those, we also have an open PR to keep the branch in sync and one of our team members is working on getting that merged.

A

Right, thank you for the update. uh Ccu commented it's great. Okay, um all right, yeah I will I will follow up on this. Thank you again to make sure that we get this in as soon as possible.

A

um I think that this one we discussed this quite a bit of whoops um in the channel, and this one from cccc was out of office. So hopefully she commented now so hopefully we can get this in also.

E

A

And the other ones I will follow up on that. Thank.

E

You for the update, thank you.

A

Any questions for dogs.

A

Otherwise, let's move on to release notes with Rodolfo.

F

Okay, our current status is green and the appear for Alpha 2 product release was closed, but we will submit a new one and for this per release. So it's not a problem and also today we will be pending for rc1 release in order to start creating the release. Notes for that.

A

All right, so why wait? Why did we close this one.

F

And we closed that, because there were an error in the comments: okay, some rebates that it didn't work well but say Anthony will submit a new one.

A

All right, okay, sorry, sorry, I missed! That sounds good awesome. Any questions for release notes. um Otherwise we can move on to comms with Frederico.

G

Yes um hi, so we had the ready for a review deadline yesterday and most of it of the feature, blogs went true, so we we do have this rest of the week until the release to to work on them. There was one of them was canceled and two of them didn't at least yet make it I'm still working in one of them and to see if it's if it goes through.

G

But but everyone replied. So it's just a matter of not being possible. We do have a contingency plan, though, which is to publish the ones that might fail the deadline near the end of the release cycle and I'm, seeing that with docs as well.

G

um We're um given that now we have a better grasp of the actual blogs that will get published. We are now prioritizing them and and settling the publication date, according to the original guidance that we defined, um I've contacted cncf for PR and the webinars scheduling as well, actually I'm already one week delayed with this. But uh now at least we have the major teams clearer, because last time we didn't um and the release article PR as everything uh in there ready for review.

G

So today we find we, we added the major thing: the the team, the release team, electrifying paragraph and everyone else and everything else as well. So obviously there will be suggestions and changes, but the there's no gap of things that are left to be reviewed.

A

And that sounds great.

A

All right, yeah I will have another look uh hopefully today for the release article all right awesome. Any questions for comms.

A

So, let's move on to release Branch management with Jeremy Alexander.

H

Yeah all right cool.

I

You're good go ahead, yeah! Oh no! You can. You can take it away if you wanna.

H

I

The update go ahead, yeah.

H

We uh so we tried to cut rc1 yesterday and ran into some issues um that I am still kind of getting to understand. The scope of I do know that we were signing images with the incorrect signing key. That's.

I

Still happening, yeah.

H

So that's that's not quite resolved um as of this morning. Yeah we're like a soft yellow, because we we did, we were able to complete the mock release and it we're currently doing a mock stage that that's running and that one usually takes a little over an hour. um So we we're back moving this morning and then hopefully we'll get through things. You know I would say conservatively by noon. Pacific time we should be done.

H

So, let's hope that things stay on track.

A

Okay, so we moved it now one day and we have the release cut the final release cut next Tuesday. Is that enough time for testing and everything.

A

H

I would think so, but I'll I'll probably defer to Jeremy on that one.

I

Yeah I think um we'll just have to be on the lookout, for any feedback comes in from anybody using RC one um keep an eye on the stability stuff, keep an eye on all the test reports there shouldn't be a whole lot of changes between rc0 and rc1 um shouldn't be any changes after this one. So hopefully things are fairly stable.

I

uh I think the biggest thing to be aware of is that the signing is still an issue, um and that may or may not be done by Tuesday I think there's probably a significant amount of work that we're going to have to do to figure out how to unravel that it applied to the patch releases that happened this month as well. So it's not just for 126, but that's a kind of pervasive issue there just to be aware of.

A

Okay, but the the signing um pod, if it's not completed until Tuesday, it's not the release. Blocker.

I

uh I think we will have more discussions about that this week.

A

All right sounds sounds like yellow, let's hope. Let's hope we don't need to move the deadline, uh the release for the release cut. You will see all right. Thank you. uh Any questions for release, Branch management.

A

So otherwise nabaroon is not in the call I think and he then wrote any updates. So I will just move on to my update, um so I didn't wrote anything down um right now. We are pretty close to the final release: um deadline, release cut. Looking at all the teams, we are kind of in a good position.

A

um Rc1 is a little bit slightly concerning, but hopefully I mean we have a lot of ice on this issue, so I'm, confident we that we make it hopefully in next this like rc1 and then also the final release cut so overall I think we are on a good track um and yeah the release theme I posted it last time. I can scroll down it's electrifying um that that's the logo, and with that, that's that's my update for today. Are there any questions, any concerns about the release, otherwise,.

A

I can see that wait. Where is it say? Scalability also also posted the green update, so that's great and with that, thank you all for joining. Are there any last topics before I close the um screen share and the recording.