Kubernetes SIG Testing, 11 Jul 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Sig-Testing Biweekly Meeting for 20230711

Description

Sig-Testing Biweekly Meeting for 20230711

A

So welcome to successing meeting. As always, uh if there's anybody who would like to uh uh sorry is newer to the space and would like to unmute and introduce themselves now, is the time feel free? Otherwise uh we can go ahead and get started after that.

A

A

I forget exactly who added uh each suggestion, but the first one is about tracing and prowl for the agenda.

A

Okay, I think it's asserted by uh John from istio who I do not see here, so uh maybe we'll Circle back to that. One later.

A

Okay, uh in that case uh Muhammad, do you want to go.

B

All right, hi there um so I have a bit of a phone problem, um so keep Test. 2 Repository doesn't have uh approvers that are around nowadays. um uh Let me see uh current approvers are our new UMC for a long time and Grant Grant is in a public phase, um so I am proposing. uh We had suggesting chairs and leads there for now and then expand it here.

A

Yeah I think it's a thin. um A chair, slash leads to find new owners. um The the only thing I know of is like I feel like a lot of the folks who used to own this uh don't anymore because they like functions, they were on, are no longer owning it. uh So my impression is kind of a lot of people just like disavowed having to own uh keep tests.

A

I agree. We should figure that out, though um I think having chair and Lead as like. Temporary owners is fine and I think that will be a good incentive to get it off of uh like that play as soon as possible as well.

B

I'm, currently working on implementing um the AWS stuff, it's already done. I just need to merge that in I'm not verified that it works foreign.

A

uh I know where to find at least one of them, so I can go ahead and yeah. If you open that PR I will uh go ahead and pass that, along to the appropriate person, yeah.

B

There's already a PR opened myself in the reviewers, but I'm gonna I'm in that PR itself to add suggesting leads as improvers and then.

A

Okay, yeah, you can.

A

That's right, if you can link that in uh the new peer and these notes as well, I think that will be good for.

B

A

That sounds good. uh The other thing that is on here is that there is a space for the maintainer track, talk uh at kubecon n, a um which I actually forgot to check the dates of this uh apologies um that will be later this year. The deadline for the main trainer track- submission, which is just basically like who's speaking with a little bit of BIOS, um will be this Sunday, so we have a little less than a week. um Apologies for not surfacing this upline earlier uh for the maintainer track. Talk.

A

um Basically all we're looking for is somebody who's interested in talking about successing um if you've contributed. So uh that does not need to be somebody who is chair or lead um as long as you are interested in speaking, that is good, and that should also uh give you a pass for kubecon um since you'll be speaking there.

A

So, uh if anybody is interested, please hit us up um and then we can work out the rest of the details for submission, as well as like uh stuff like preparing the talk and slides and whatnot will come later. I will pass along deadline or anything for that, um but yeah. uh If you're interested- or you know anybody who might be interested, uh please uh let us know yeah Chicago November, uh thank you for finding that Matt. So that should be uh plenty of time for actually preparing to talk there.

A

um The only thing we need for submission is basically just like. Have some folks who are interested um I think we can change this up later as well. uh We just need to notify like if we're changing speakers and whatnot and I am going to sillies and take the put the links in the notes.

A

A

I should say: maintainer track talk or cubecon n a.

A

All right, um I think that's it for that we can go ahead and circle back to the first agenda item. Unless anybody has anything to say about uh uh talk there.

A

um Yeah, so I I, don't think we have the person who originally added the suggestion. But if uh anybody is interested in talking about tracing you in proud option feel free too.

A

um This one linked at the top of the agenda I'm just going to take a brief look.

B

Yeah I looked at that issue um I like John's proposal, um but it looks like you already wrote the code for it. He needs somebody telling.

C

Me I would like.

B

That um I'm gonna race prior to merge and as long as it's future gated, it's fine um as a proud maintainer. I would like to use this in the brows that I manage, but yeah yeah.

A

I think this should be a pretty good option, so I think the main thing is just to make sure that the folks who are maintaining policy it. So that's good um I, think we can also uh I can try and surface this to some of the Google pro folks, um yeah.

A

uh Is there anything else that folks want to say on it? I think I mostly just agree that, like this looks like a good idea and I, don't think it's too controversial.

A

All right, I think with that um sorry, the formatting on today's notes is a little weird and I'm not sure why.

A

I think we come to the end of the agenda. So is there anything that anybody wants to mention that wasn't already on here.

A

All right, I think in that case we can call it good. uh So thanks everybody for joining. Hopefully this is good, um feel free to take a look at some of the links stuff or bring up anything that was mentioned here in the chat uh and otherwise yeah have a great rest of the days.

B

Thank you both. Thank you. Thanks.