Kubernetes SIG Release, 26 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20211126

Description

Kubernetes Release Team Meeting for 20211126

A

Hello, everyone great to have you back to this beautiful burnout meeting on the november. The 26th- I'm max will be your host for today and please remember, and we need this meeting so we're running under the code of conduct of the cncf, which falls down to be awesome to each other, and let's run shortly through the current status of the release 123..

A

We do not have any big open topics at the moment which we need to discuss a short hint for you. um If you have already some points which you would like to highlight, and the retrospective meetings, which will later come up, you can already go to the retro document and add your notes so that you will not lose them or lose your thoughts, ideas and wishes of change.

A

With that you have anyone from enhancement in the call.

A

Otherwise, all the good people spent the time on thanksgiving, which is also great and deserved.

A

Moving on to ci signal with leo.

B

Hello, so our current status is yellow. We have 14 passing jobs and four flaky ones in master blocking in mason forming. We have eight passing and thirteen flaking and we are tracking them um for the fading one in mason forming. This is one uh test which is now fading for quite a long time, and it's also reported a couple couple of the flaky ones are also reported, so we are tracking them and then um 1.23 the massive blocking and mass informing stuff.

B

um So we have one failing which we reported today um opened up the um an issue um and under mass informing, we have two failing jobs, so we are looking at them and maybe we will also open an issue, but that's it. Thank you.

A

Cool beside the the failing ones um is the release candidate quite stable, or does it pops up here and there's some additional flakes? We see here two two flaky jobs on the master, um but maybe you've observed some other behaviors or tests which are not running at all.

B

um So when we are talking about the 1.23 uh massive blocking, this is the one you're.

A

B

In so um the flaky ones, I did not go get into too much detail because they're quite new um about the failing ones, they're, a lot of um jobs that are failing, but they all seem to be like, uh like. I think the source is the same one. So a lot of jobs are depending on one um one source of the error. It seems like. um um I don't know if fossen um looked into that, but this is something.

C

Yeah, that's true, yeah, that's true, and regarding flaky ones we are watching them. So if they persist to flake, you're gonna create a nice issue for each one of them. So we have our eyes on everything on test grid, cool, perfect.

A

Thank you guys back to just kristoff.

C

Yes, hello, so our current status is um yellow due to the fact that we have um critical issues and um prs open. um We have two critical issues um about pumping gcd, client version and another one about go modules. um Both of them are actively being worked on so nothing to be concerned. Of um just a note.

C

We also have the etcd issue as an important issue text so due to the fact that this both labels, we see twice in our reporting um about the two um critical pr's um both of them are approved, but they are currently on waiting schedule.

C

So nothing needs to be done here, um yeah, that's it.

A

Cool looks good. Thank you, doc's with me.

D

So our current status is green, uh integration branch is healthy and our team has reached our authors for the remaining uh peers, which are currently withdrawals.

A

Awesome. Thank you very much.

A

uh Release notes.

A

What's going down.

A

E

Our status for the week is green and we are working on the 1.23 leases, rc 0pr, and that would be submitted soon. I suppose other than that there are no open, prs or api's that need to be merged or have been approved.

A

All right cool, perfect. Thank you very much um for comms and release branch management. I think we do not have someone in the call. um As far as I know, it looks quite good on the comp side um and also on the release branch management. As you obviously see the release, 1.23 release candidate um went out. uh It was a little bit bumpy, but it make it through it. So everything is fine here. I guess next milestones. We have already highlighted it on the november 30s.

A

Next tuesday um we have actually the um dog's deadline, or at least the docs readiness deadline which we are looking up, and we also should have all the feature blocks um already in a review state or in the well situation that we can review the feature blocks and start scheduling it for the release, which is actually in.

A

Is it two weeks and roughly two weeks cool.

E

A

It's very close: it's going to be very, very fast. Are there any other topics from your side.

A

That's what it sounds like then awesome work, everyone thank you very much have a great day and have already a great weekend see you soon. Bye, bye, see you soon. Thank you. Bye.