Kubernetes SIG Release, 21 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20221121 (v1.26)

Description

Kubernetes Release Team Meeting for 20221121 (v1.26)

A

Hello, everyone, um my name, is Priyanka and I'll be the host for the meeting. Today we are in the week 12. um of the 1.26 release cycle and today is November. 21.

A

I will uh request everyone to add their name to that ND list, and we can go ahead also. uh This meeting abide by the cncf code of conduct, so that pretty much boils down to please be nice and excellent to each other. Thank you.

A

um We do not have anything in the open discussion other than the retrospective document. If you have any feedback or comments um or any retrospective item that you want to discuss uh as part of this release cycle, please feel free to add it to the document so that uh we can move to the release team updates enhancements.

A

um Anyone on the team on the call from enhancements team.

A

um If node uh I am assuming, it would be same as last week um since we are past the enhancements. Please and code phase now uh I'll move to cic number.

B

Yeah so hi everyone, the current status of CI signal, is yellow because we have one failing job in master informing and we have already opened an issue for the same, also playing the respective set. That is sick note, and they are looking into that.

B

Apart from this, there are six clicky jobs in master, informing and seven seven play key and master blocking. That's all from our team.

A

um Thank you, uh I just take the feeling, a massive, informing feeling issue and believe uh folks have reached to the problem any comments. Any any questions for CI signal.

C

Hello, yes, I'm Meha, like on behalf of CI signature team uh I, have followed up on the failing issue like uh I, have reached out to Sig note and uh I got to know like it's not blocking for the release, and they are. uh They will try to fix it as soon as possible.

A

Thanks so much thank you. uh Let's move it with bug triage.

B

uh Yes, government stuff.

D

This is green, uh there is no obligina.

A

um Thank you uh any any comments, any uh anything for bakria's team.

A

Cool, uh let's move ahead with docs updates.

E

um Hi, uh well, we are in a state status, yellow because we have three.

E

Triple requesting draft mode and right now, everyone every pull request, has to be ready for review. That's the reason.

E

um Also I have a pull request. That is like nine days that is open, I, don't know if someone I will put here because in the chat zones uh is to sync the main branch, the depth, 126 and I. Think that's all I, don't know. If you have some question.

A

um Thanks for the updates.

D

So um are the three ones um still the ones that I think reported like one week ago so yeah? So basically nothing really changed on that side. So folks are still not responding to um opening PRS about.

E

The documentations that.

A

E

A

E

The draft mode all the Caps has documentation. We don't have any any without the pull request, but yeah it's only because they are. The deadline has passed about it.

D

But all all enhancements have no docs at least once.

E

So- and this has yeah so.

D

This process is moving forward or do you need any additional help with ping people or getting this no.

E

I, wouldn't I will try to reach these three drops per request about today. Go ahead to to awesome.

F

E

And yeah I will, in the next thing, I will see if, if it's even better.

D

All right sounds good.

A

Thank you. Thank you, Karina. um Thanks for the updates, uh we'll move ahead with release notes and what also.

F

Hi, our green status is green and we will be working on the major teams and node issues. Draft document from now and in the following weeks also a couple of six confirmed that they don't have mere teams to report in this cycle. So we are good for now.

A

Sounds really good. Thank you at all for the updates. uh Any questions for at least not.

A

uh Good, uh let's move it with comms uh with David.

G

Yeah, hello, everyone um recurring status is green. So far the mid cycle, deprecations and removals block was published last week and also there's already an initial draft of the release. Article itself, it's in progress and all the in tracks enhancements or the ones that opt in for future blocks are being full.

G

The deadline for initial draft review is coming next week, so we are providing reminders to enhancement Outsource about this, but yeah so far. That's the status.

A

um Thank you David. Thank you for the update uh any. If you need any help, just feel free to reach out to us we'll we can help you reach out to the others, um any update, any any comments or com stream.

A

If not, uh anyone from release Branch Management on the call.

A

uh Anyone have any updates from release management. If anyone aware of you yeah.

D

So so the next cut the RC one card will be in eight days so on Tuesday next week, um but everything looks I. Think fine at the moment for CI signal Maybe. We can check if there are like any flakes, but besides that everything should be fine. There was one issue open to update the test grid, 1.26 dashboards, so basically the test dashboards for our specific release for 1.26 and these needs to be merged, but I ping, the the leads in enchanting over the issue.

D

So hopefully this will be get merged today or so so we can observe the project ports properly and that's it.

A

Yeah, that's true yeah and just to add I say there are three Cherry PR's, also open on KK, which are waiting on release, Branch money or release manager's approval, yeah.

A

That's what uh let's move to our Emirates advisor uh navaroon, if you are in the call.

A

um Looks like no so or do you live again.

D

um It's my updates, uh I'm, currently reading over all the Caps to get a better understanding what details changed so, basically, with code freeze, we now have like the exact number okay, these caps are getting in the release and some did not made the deadline.

D

um So I read over to all the caps and add some some ideas to the release. Major themes block on the way which David already linked above in the comms update and I'm, also working on the release theme.

D

Hopefully I can announce it this week, so every release has a name, so the name can be anything and also a logo which gets released over the release, block and yeah. That's that's! Basically, it.

A

Thanks Leo, we are all looking forward for the release team um yep. Thank you uh with that. We I don't see any updates from scalability. uh Anyone on the calls from sex, scalability.

A

If not, uh we are at the end of our meeting. uh Anyone wants to bring anything before we stop the recording.

A

If not, uh thank you, everyone for joining the meeting, uh I'll go ahead and stop the recording.