Kubernetes SIG Release, 12 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Release Team Meeting for 20220412

Description

Kubernetes Release Team Meeting for 20220412

A

All right everyone, uh good morning, good evening good afternoon, wherever you are, uh my name- is james lavrock. I am the release leader for kb24 and I shall be your host today. uh This meeting, as with all of our meetings, is covered by the kubernetes code of conduct.

A

uh If you are here with us, please place your name on the attendees list um yeah. I guess we'll just jump straight into updates, updates, enhancements.

B

um I'll take that one, so um our overall state as a screen. uh We are looking at this one enhancements2593 whether this should be included into the release or not. There's an ongoing discussion thread. um I've linked for it's going on in sig release for context. The enhancements was.

B

uh The enhancement issue was removed from the milestone after code freeze because there was no code uh marched by the time, but there was there was a pr that was merged after the code freeze and uh that is introducing a new alpha api, but we do not have the docs um available for that yet yeah.

B

So we are one. Thank you.

A

Okay, thank you very much for the update um yeah I've been following along that thread, so I guess we'll see what the outcome is and we'll discuss that async, but yeah.

A

Okay, all right any questions or announcements, nope all right! Thank you. Priyanka uh see. I signal leonard.

C

uh Hello, uh our status is still yellow um the new flaky issues that I mentioned yesterday that we investigated have been reported. They all connect basically this to the same source, and it looks like it that this is already resolved, so this is quite good. All those basically jobs mentioned basically in the list, all those related to the same same course of issue, and they seem to be resolved, as I said, so, this is looking good. Besides that, nothing much has changed so still the same status.

C

Everything is looking okay, I would say.

A

It's good to know, I was hoping things would stabilize a little bit, so it's good to see what they are all right. Okay, any questions to see a signal.

A

Nope all right well, thank you very much for the update uh book triage.

D

Yes, our status is still in the same. We are still in yellow. We still have that unreleased blocking issue and one uh important soon, pr, which is the jenkins yeah other than that we are all the same.

A

All right well, hopefully, that release blocker will be resolved today if go 118.1 cuts, so we should be, should be in a good state. Maybe yeah one hopes on dreams all right. Okay, thank you. Any questions for book triage.

A

Nope all right, thank you! So much uh docs, I don't think there's anyone from ducks in the cool unless I'm mistaken nope. I have no particular updates. I assume they're good as they were. Yes, I think I had a green before um releasing it.

E

Yeah, hello, everyone, so our current status is green as opposed to yellow, which was uh yesterday. The alpha draft pr has been merged and all the website appears for. The beta0 have also been watched. That, apart, has mentioned major themes. Discussion and known as discussion is up on github and there are still some conversations going on over there and that apart, there were some patch releases for formal release cycles and uh different release spaces from foreign cycles that were also incorporated through vrs.

A

All right, okay, great! uh Thank you! So much uh does anyone have any questions for release, notes.

A

No all right good! um I did see chris just jumps on the call chris did you have anything for us from dogs.

F

Yeah give me two seconds to paste it in me.

C

A

I'll go back to you again. Sorry, I'm late.

F

A

No, that's all right uh early.

C

A

Yes, all right comes tv.

E

Hey hello, hi, so uh I've marked a state marked our status as yellow because we're still waiting on status of major themes. The discussion is on so I would appreciate if people can put on their reviews and comments there, uh the feature blog pr is uh in wip mickey opened up yesterday. I think, and it is up for review. I saw some of the reviews there, but more reviews are welcome.

E

uh We will be reaching out to feature blog writers and the sick dogs uh block channel to get a review on the feature blog and I guess that is it yeah. Okay, all.

A

Right does anyone have any questions for comms.

A

Yeah, no all right! Thank you so much. um I don't have any particular update from release french management's and joseph. Isn't that's cool um so I'll just do my bit, then we'll go back to docs, um so there's a thread about miss enhancement. This is what priyanka mentioned earlier. um So hopefully we'll get something about that. There's still a discussion going on about release delay. There is a sig release. Release engineering meeting today, which I suspect is probably going to come up into uh failing that will probably discuss it tomorrow.

A

The current suggestion seems to be to delay by two weeks um whether or not we'll actually do that is to be confirmed at this point. So it's not confirmed yet, but that's that's what we're looking at um and we're also discussing not doing these not doing these daily burn downs unless we absolutely need to there is a discussion thread open which can be summarized as we'll only do one or two of these a week and then the rest will just do threats in slack.

A

um My intent is to have a decision, make a decision on that in tomorrow's release, team meeting um and then go from from there. So if people have opinions, people add them, please add them to that thread. um Anyone have any questions for me.

A

Yep all right, in which case we will jump back to docs chris.

F

Yeah thanks um we've made really good progress. I I think we're green though today is the deadline for having all docs ready. um We are down to uh four um that are ready for review and not yet completed, uh and then the docker shim, which is its own story, I'm trying to look and see what it was yesterday so yeah we managed to get seven seven merged yesterday and down to only four left for today, so pretty good shape with that um the docker shim is is kind of the issue um we are meeting in.

F

uh Let's see three hours from now, where we're gonna try to blitz through, we have a lot of stuff, that's just sitting there in the state of um yeah. We have a pr. Why isn't this merged?

F

So hopefully we can do a bunch of those uh today and then really just focus on um on just uh getting the ones that really that progress hasn't been made on, and there is still a handful of uh issues and prs that that are not yet done, um but like most docs people were always happy to have the project slip.

F

So if you, if you slip a couple weeks, that will just only help us get all that done.

A

You're welcome, I guess.

F

All right, that's it that's about it! Any questions.

A

uh No no particular question for me. Anyone else any questions.

A

No all right: okay,.

B

A

That's everything I think so, I'm going to end the recording, I said, there's any particular things to bring up in the recording nope all right.