Kubernetes Cloud Provider Special Interest Group, 8 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SIG Cloud Provider 2022-06-08

Description

Agenda: https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/

[elmiko] gcp-related PRs for discussion:
https://github.com/kubernetes/cloud-provider-gcp/pull/333
https://github.com/kubernetes/cloud-provider-gcp/pull/313
https://github.com/kubernetes/kubernetes/pull/84466

Kubelet credential providers to GA
https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers#beta---ga-graduation

A

A

Everybody it is Wednesday June 8th. This is the Sig kubernetes sick, Club provider meeting. um We have a couple items on the agenda today, so I'm gonna go ahead and get started. Please add yourselves to the attending list.

A

All right! Well, we'll get kick it off with a bug scrub as usual.

A

A

I, don't know them all right. Aws classic BLB is created with a relevant azs.

A

Okay across some little bouncing true, really busies.

A

A

Why are they choosing Crosstown.

B

A

Balancing, if they don't want.

A

Multiple azs, perhaps that's the problem.

A

But better, uh uh why do I always use.

A

From the browser that I don't normally use uh anyway, but all right give me one second I'm gonna, um it's easier to just switch over to Firefox and stop sharing really quickly. Yeah no worries.

A

A

A

A

Just going to accept this one and take a closer look.

B

Cool sounds good.

A

A

I do remember seeing this one. Kid would make successive calls to BC Humanity service, which has rate limits.

A

Wait this one is already triage accepted.

A

Are we oh it's because ignode I think also needs to accept it. um Okay, yeah so I've taken a look at this one and service selector outfit is ignored.

A

This one still needs triage I think we were gonna, try to accept it last time which I did.

A

Why does it still need triage.

B

What was that comment from Bridget? Was there going to be a follow-up from one of the Azure folks.

A

A

So they're using an older version of kubernetes, it looks like.

A

Please try 124 Okay, so potentially this is resolved Maybe, if I don't know purchase is on, um looks like not, but I'll leave it to bridge it, but.

A

A

I wonder why my triage accepted didn't stick.

B

Yeah, that's weird.

A

Oh there we go okay, so.

A

um Let's go ahead and go through sub project updates. I will just give everyone a minute um whoever's here to go ahead and fill out uh and then I'll just read through or if anybody has something I'll stop by.

B

A

We have some new releases uh I. Think it's 120 through 124.

A

C

We did the clean cut for the release 123. and we started working on release. 124.

C

A

um Okay extraction migration, I missed the extraction migration meeting last week, um but I think we can just pull up the agenda really quick and see or I, don't know if anybody else made it and wants to give an update.

A

Okay looks like there was not.

A

All right, um any other updates for sub-projects before we move on to the agenda.

A

Cool all right spell me, go take it away.

B

uh Yeah these were a colleague of mine, uh Mikhail fedosan had opened up a couple PR's here and there was actually an old PR to the entry stuff.

B

um The first one is like a bump to 1.24, but maybe um it seems like maybe Jakob is already working on a 1.24 update, so that I guess that might be obsoleted by my work you're doing now, but he just he had been having trouble getting the the testing to pass um on that 333 PR, the other two PRS um are about reusing the instance groups um yeah, so the these ones. uh This one was closed and there was another one for the entry it was closed.

B

But this is I guess um you know, and Mike has more details in the pr here, but the you know basically I just wanted to kind of raise the issue and see if we could get some folks from Google to take a look at this stuff, um because it's causing a bug for us when using and I'm gonna probably get this wrong, but when using load balancers with internal using internal load, balancers with the private, vpcs and I think this helps alleviate that problem.

B

um I. Unfortunately, I haven't worked on these PRS, so I'm, not he just he couldn't make the meeting today, but I wanted to bring them up and just kind of get some attention here. um So I I don't know yaakov. Maybe this is something that you know that you or your colleagues can take a look at or maybe give a give some comments on.

C

Sure I think I would try. I will just try uh to find the right person to look at those PRS I, guess that someone from the networking would be a reasonable person to handle those problems. uh uh Actually, at the beginning of this year, we had some kind of a transition period between multiple teams happening for this, this repository in this project. So this could result in a few uh Light reviews and some tasks that were kind of dropped to the floor.

C

So sorry for that uh try to find someone that will take a look at this code, cool.

B

Yeah yeah no worries it happens. That's why I just wanted to bring it up. Maybe just get some attention on it, but I appreciate any any comments that you or your teammates could add. That'd be great.

A

Looks like they're both closed, so you might want to reopen them. If you want.

B

Right, like I, need to get I need to kind of get back and figure out what was going, why they were closed from like I think one of them was closed because it just became stale, um the other one I'm not sure about, but they might have both gone stale and just got closed by automation. So yeah I think I'll make a note to kind of figure out if we need to reopen them or what looks.

A

Like the docent closed this one, so okay.

B

Yeah I don't know yeah like he had kind of wanted to bring these up I'm, not sure why he closed that one, um but yeah like I guess this is still a problem. That's affecting us, I I, think the entry fix is kind of much older I, don't know if if he was trying to replicate that here or what- but maybe maybe I can get him to show up to the next meeting too um that today he couldn't make it. Unfortunately.

C

Well, uh if you could uh reopen those tickets, those pull requests. uh uh I will assign someone from from the networking to look at them. uh I'm I, don't have hike expertise around the load, balancer stuff, so I I'm, unable to help with this. This topic.

B

Okay, cool! That's awesome! Thank you.

A

A

Let me go, you can take that action item if you so choose um anything else on that or shall we move on no.

B

That that's it for me. I just wanted to kind of get some attention and just raise the issue like what, with the 1.24 release, are you working on the rebase for that as well?.

C

uh I'm doing the cluster directory or something close I.

B

Meant the cloud provider so yeah like this, this PR here that Mike has put.

C

Up yeah uh the process to bomb, but the repository requires getting some stuff into the cluster directory, the the one massive part that is shared with the KK Repository and in this position it's strongly hacked and I will need to resolve the problems that came up during the any differences that came up between the 123 to 124..

B

So but that's some you're looking at that right now, right, yeah.

C

Yeah, this is something on my but uh more or less right now. I hope that I I would have time to do this last week, but other other tasks and other applications.

B

For sure it happens, thanks cool.

A

All right so um I just wanted to take a look at our release. Schedule uh oops, that is 125. I, believe next week is enhancements. Freeze.

A

Let's take a look.

A

um So and make sure to look at the PST time which I'm in the state of last time so um Thursday June 16th, so, is that next Thursday it is yeah, um so any changes to enhancements that we want to get in before for 125. We need to do by next week, um which doesn't give us a ton of time um so yeah uh anything that people have on their minds.

A

um Let's, let's talk about it here, um I think just in general of one uh also just 125., 25 stuff. So for me, um web hook framework that we were working on for the last release, um it's probably primarily what I'm going to be looking at, um but uh so uh 124 leader election went GA. So we're good with that.

A

um Does anybody know the status of the uh credential exec plugin stuff? um Did that go ga, and maybe we can scroll down here and see yeah I I, don't know on that. One.

A

Search migration.

A

I think we'll probably need to look at the extraction migration.

A

All right so leader integration to ga um cubelet, credential provider, graduation to Beta.

A

A

uh The probably a question as to whether or not we want to take it to GA um I. Imagine that we do.

A

Okay, so we probably should update the cap, at least with um beta, to GA graduation criteria um and then decide if we can do it. This cycle.

A

Let's see foreign.

A

Does anyone want to have Cycles this next two weeks to look into this one.

A

If not I will try to, um but if anybody's interested in it or or have some free time, which I know we probably all doubt but um and the off chance that somebody does. uh This would be a great great place to to help out so I'll leave it open um cool. Let's see so, let's go back to.

A

The original mirror lookbook, it's your serving okay, that's all I know about. Does anybody have anything else that they I mean I know Walter is working on um testing, and uh you know this. The last known good proposal pulling testing out of um kubernetes 4 fixing broken tests after we disabled Cloud providers there.

A

So I I'm definitely interested to hear an update from him on that, but other than that does anybody have any topics that we need to address for 125.

A

Cool all right. Well, um let's all like definitely think about it. um You know like think next couple days, Days, ideally before next week, like thanks to what your cloud is doing um any issues that you're running into any changes that you want to make for um for 125 to uh to. You know any of the shared libraries and um let's, let's get started on those changes early so that we can get the merge other than that I. Don't think I have anything else.

A

um Cool yeah, any other topics for the group.

A

All right get some time back. Have a good rest of your week.

A

See you in two weeks or um at the extraction meeting in the week.

B

Cool thanks, Nick.

A

Cool. Thank you.

C