Kubernetes SIG Testing, 8 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Testing Meeting for 2022-03-08

Description

Kubernetes SIG Testing Meeting for 2022-03-08

A

B

A

So I think ben might be out this week.

C

Would that be eddie and daniel report again.

C

Probably you seem to be the monster.

A

A

I'm not sure if anyone else is around.

A

I also don't have the host key.

A

ah Alvaro is here: well, that's good!

A

A

So I'm pretty sure that ben is out and aaron has been out for a bit.

A

There are some things on the agenda.

A

We'll give folks a few more minutes and then we'll kick it off.

D

A

ah There's coal.

A

Alvaro or cole do either of you have the host key for this call.

E

F

I do not either okay.

C

But the recording is already running so, if you need to, if we just want to go with it, then trim it later.

A

Yes, sir good call.

C

But then you probably can't show your screen. I think.

A

No, we definitely can't share screen without a host key, um alright. Well, we can at least talk through some of the stuff on the agenda, um so the call's already in progress, uh which means the recording, is happening so don't say anything you don't want recorded public on the internet um and I guess let's get started so cool, I'm guess I'm filling in for ben today. um Thank you for coming to the sig testing uh bi-weekly meeting for march 8th.

A

My name is eddie zaneski and I'll, be your host just a quick reminder that this call in all calls and projects under the kubernetes org abide by the cncf code of conduct. So please be excellent to each other, and with that do we have any new folks on the call that would like to introduce themselves.

D

I am newish. I've been to one other one of these meetings. I'm tim, I'm from uh intel corporation just here, observing for now.

A

Awesome welcome tim.

A

Any other new folks.

A

Cool so going through the open discussion items on the agenda, uh we have an update from linus on the products. I don't think lions is on the call.

A

But it's live and it's tracking towards being done, which is awesome.

F

Yeah, I think, we've uh I can kind of speak to this a little bit. I think the site is uh up, but there's not really much content there. Yet it's just kind of the the skeleton and all the the infrastructure for it so yeah. I think next steps are to start migrating docs over.

A

Awesome great work to y'all um any other thoughts on products in that initiative.

F

um I think linus is planning to to migrate the existing docs, but once we get to that point, I think it would just be kind of the situation where we want contributions to them. If people think that there's anything missing, that kind of thing.

A

Cool and was that trump that was tracked somewhere right, the the proud docs.

F

um There's some github issues for it uh and uh yeah.

A

F

Is that what you're referring to or were you expecting uh something more yeah.

A

Was there a cap or was there an umbrella issue.

F

um I will ask linus about that. I don't recall to be honest.

A

Okay, I don't see anything in enhancements, but okay cool- that's awesome. uh Paris put on here that she wants us to finish the annual report, which I guess we'll circle around to um and.

A

Looks like we have a couple other items.

A

Is this um is sanchez on the call I'm terrible with names? I'm sorry.

A

Doesn't look like it.

A

Getting started with integration testing on kubernetes going through the repo is confusing.

A

Yeah, it can be intimidating at first. um I think there are definitely some recorded walkthroughs from past cube, cons and contributor summits, and if they aren't linked in the documentation, we should definitely get them there.

A

Anyone have other thoughts on that.

C

Agree, documentation always lag behind not just this.

A

Yeah yeah aaron has given plenty of um walkthroughs in the past and they are definitely strung throughout different sick testing meetings. um We should probably get one recorded independently and we can put that on there too. um So we can maybe talk about that in the future.

A

If we have a volunteer, who knows how to navigate that very well and wants to do it.

A

uh Any other thoughts on proud testing and documentation.

A

Cool uh rhiann, you have a item on here.

C

Yes, um if you click on the link there by um 7 8 march, and you follow that you'll see, which is a little uh-oh if the link's working so I'm making a proof, it should help the link to work. Is it working? No, it does not seem to work. Sorry, let me just catch it here copy. I don't know why. I don't have edit rights on the doc. I don't normally do. Okay, if you have a look at that link, you'll see that um that test.

C

Now I hadn't slacked yesterday the day before yesterday, and then I had the logs for seven and eight, and today I've got the logs for eight and nine. It seems to something is removing the logs and for us to be able to that. This is running green.

C

Every time I check it's running green, but two weeks down the line, I want to prove that it had two weeks flag free to get it merged, for conformance for which we already have the promotion lined up, but I am in a corner for proving that that everything went green. So I'm not sure if something changed that the logs are not showing.

C

If there's anybody on the call that know about, I posted it in slack in sick testing, but got no reaction to that.

F

um I don't know what's going on off the top of my head, but I have some ideas. One might be the days of results. Setting is kind of how the garbage collection mechanism is controlled for that. um So I'm not sure exactly where that would be defined for this, but that would be one thing that I'd go. Looking for.

C

um Anybody specific that I should bring to the local pet.

C

I'm sure who's in charge of these logs.

F

um Yeah, I'm not sure how to determine the best job owner for that. Besides, like looking at the kit logs for the the job configuration.

C

I'll see if I can find any changes that was made because.

E

It wasn't like this.

C

um Previously, on previous tests, you always just kept running, and you easily at least had two weeks window to prove your your flag free test. So this is a little uncomfortable for us for conformance testing.

C

Okay, thanks I'll go look at that.

C

That's it for me, thanks eddie.

A

Cool that was all the other items on the agenda. Does anyone have any others they'd like to talk through before we look at the annual report.

A

Okay, I'm going to drop in the running dock. We had from last time.

A

And it was this one: this was our annual report.

A

A

Well, we needed to clean it up and get it shipped.

A

It doesn't look like any edits were made since the last time we met.

A

I unfortunately don't know enough to fill in all the fields here. I think we filled in as much as we could.

A

We do have alvaro. Are you still actively working on prow? Is there anything you want to highlight from the past year in here.

E

Yeah, there are probably a couple of things so off of the top of my head. Most of our got support for github apps authentication,.

E

We did some work for conflict sharding and, probably to some degree showers work regarding the baylet application as well. I mean it partly had happened last year.

F

Do you have any sorry go ahead? We did a lot of work on proud over the past year. I think a lot of it was geared at applications for other open source communities or for other uses for prow, um like a lot of the stuff alvaro just mentioned, um there's also the uh I think the bazel deprecation is one of the big ones. That's happened recently, um I'm sure there's a few more things that we can try to escape together.

F

I didn't have a chance to look at this last week, but uh I kind of try to find another item or two.

A

um That's a good summary, though you said he said: prowl work for other open source projects and communities yeah so like.

F

The github app support, um you know, that's obviously a great feature for proud, but probably wasn't really. It hasn't really been used by the kubernetes community. um We now have uh like validation for unknown fields and job config, but that can't be enabled by the kubernetes community, because there's just too many jobs that are broken and we can't reasonably fix them all um yeah, so there's been getting new features, but uh kubernetes hasn't always been using them.

A

Cool awesome: um do you have any? Are there any big, pr's or issues that we can link to in here? For those.

F

Do we want to be calling out the things that don't benefit the kubernetes community itself.

A

I don't think it hurts because prow is, you know kubernetes native ci cd, so it is a product of sig testing. So if we want to, if not that's fine too.

A

uh Anyone that can speak towards updates on kind that were made.

A

What about the end-to-end test framework.

A

Cool- I uh I guess I'll just open this pr, as I can with what's in here and uh yeah, we can go from there.

A

Any other sub-project owners want to make sure their work's represented and their contributors works represented. Anything to call out.

A

Any specific areas where we need help in certain sub-projects.

B

I had a question regarding kubernetes using the test framework.

A

Cool, uh what's the specific question.

B

Yeah, it's a beginner question, so I was trying to write an integration test, but I couldn't.

C

Really figure it out very.

B

Well, I dove into the code, but I kind of got lost in it. So what's a good way to start.

A

Oh, I think we talked about this before you joined. um There are some recorded walkthroughs of the test in for a repo and the proud jobs. If you look through the past contributor summits and past cubecons, so look through like the cncf playlist for past cubecons and look for the contributor summits and there should be some walkthroughs in there. um We also agree that we definitely need to get some more updated uh information there as well.

B

Because for e2e testing I saw it's kind of detailed, but uh in the other, uh in the other type of tests, if anyone wants to write they're gonna be stuck uh trying to figure it out for themselves. So that's why I also wanted.

A

B

A

Yeah, I don't know if we have anyone on the call who can speak to the specifics of the end-to-end test framework.

A

Yeah, I don't think so. We got a bit of a light call today.

C

And um also um looking back at previous um recordings of this meeting, also with you with some some insights about how it works. So it's going to take a bit of time if every other documentation could be better agreed. But looking back at previous recordings also give you some insight on how the sig work.

C

Hope that helped.

A

Any other thoughts comments on the meeting today or the annual report.

A

Cool well thanks everyone for coming um I'll, synch up with steering, and um maybe we can get some steering support going forward.

A

Thanks everyone.

C

Have a nice day see you later cheers thanks.

C