Kubernetes AWS Provider, 11 Dec 2020

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes - AWS Provider - Meeting 20201211

Description

Recording of the AWS Provider subproject meeting held on 20201211

A

Hello, everybody and uh welcome to cloud provider aws. It is december 11th 2020.. um This meeting is being recorded, so please respect the community uh standards and let's go ahead and get started. We do not have an agenda right now. So if you have anything that you'd like to talk about, please add it to the agenda.

A

Otherwise I was just going to um give a couple of updates um on the cloud provider aws project, so yeah go ahead and add anything to the agenda. If you, if you have anything otherwise, I will just start talking a little bit. um So a couple things um one first, I would just like to thank nicole she's, been doing a lot of great work on the v2 sort of uh proposal implementation.

A

um So maybe we can get to some of those pr's that are open. If you have anything that needs reviewing nickel, then. Secondly, we have um some. I guess I could potentially share my screen. We have a.

A

I did just a little bit of work on docs. It needs quite a bit more, but um so there's like a live doc site now. um So let me try to share my screen I'll see. If I can pull that up really.

B

Quickly, I just made you the co-host so awesome.

A

See can you see? Oh, I think I remember you. What's that better? um Can you see the cloud provider aws window? We can yes and looks good great um cool, so yeah it's just uh using. I think it was. It was using what andrew had initially um set up, which is this uh git book or whatever um so there's uh just some really quick information. I started doing the like how to set it up with cops um section.

A

Obviously, you know still needs quite a bit more um work, but if you I encourage you to um everyone, to just kind of you know, add um sections as they see fit. um I could definitely use a section on the the v2 provider um and any other ideas, um yeah just file issues or bring them up here.

A

um Let's see yeah the second uh any questions on on docs or any any thoughts on what where we, where we need document documentation the most.

A

I think one thing that we really need to do is uh just put a probably in the main readme we're following the convention, for um it was suggested by sig cloud provider to have the major and minor versions um reflect the kubernetes version that the the build is compatible with, and then the patch version would just be like a.

A

I don't know like a build number kind of, or just like the specific to cloud provider version. um So I think we probably just need like a quick blurb about that on the homepage, um maybe a timeline of where we expected to be going, um and probably some information about too. Just because I think I already saw some comments about like is you know: is this going to be compatible? How do you expect people to upgrade like um just questions and.

B

Yeah that dark side looks really great. I think- and I like that convention on that- I think that makes a ton of sense, uh at least until we can uh not have to worry about the compatibility of the minor version. So, yes, that makes time sense. Yeah very true.

A

um Cool, so the only other thing that I can think of too that's worth mentioning um is just the um the prow job that justin set up uh justin. Do you want to talk about that.

B

uh Sure I mean uh nick contributed uh initial support, uh experimental support, I guess for uh the ada breast care provider to chaops, and so we plumbed, we don't expect it to fully work, uh but we plumbed that, through into a uh periodic job that should run daily thanks to nick for reminding me not to run it weekly, because that's not enough, uh and so somewhere uh in kate's test grid, which we can't find, I can pull it up. uh There should be a sort of one-off test. Wait that can't be right.

B

That's not the chaos job. Is it? That's probably. No. I don't.

C

B

Okay, uh if you go to the top yeah you can, if you go to the green checkerboard, you can search uh in the top you can type like. uh Don't do that? Do I do copper, provided ws or something.

B

What did I call it? uh I have to look at what I called it, um but anyway, there's there's a job. uh Apparently it is uh it's not passing, which is not unexpected and uh oh, it's try scenario. Sorry scenario might scenario.

B

There we go there, we go, we have a couple of sort of one-off scenarios, um and so we have it running uh daily, which is at 2 30, pacific, and uh it is currently failing- and that looks like it's failing pretty hard, but we will nick and I we can figure out, what's going wrong and hopefully get some uh progress there. We still, as I understand it, we still don't expect it to pass all the e to e suite because of volumes, but uh we should at least get more of more.

B

We should get individual test results.

A

Yeah yeah and it's uh I I did take a grocery look, it's just because the the way we're handling it's. We only have builds for 118 and and 119 as of as of yet uh there's a pr for 120 waiting to be merged. um So I think we're just not handling the case where it's a version being passed in that we don't expect.

A

So we need to either need to pin the version or uh we'll probably need to pin the version.

B

Looks like it might even be v121, which is terrifying.

A

Yeah, so as soon as we get that uh 120vr, we'll probably want to just pin it to 120.

B

uh Or 119., I think there are actually other things going on in 120, but uh yeah got it. Okay, cool.

A

Cool, that's all I wanted to mention. um Oh actually, there was one other thing, um so I think kubecon eu next year. The deadline for talks is like in a couple of days or for for cfps um we get a.

A

I believe we get a free slot, so um I can just go ahead and like submit a talk just to kind of preserve our spot. Do you think we should do that.

B

Yeah, I think that's a great idea, especially because I mean I think, there's a lot to talk about with that with the um like the v2 idea. In particular, I think it's an interesting one uh to talk about. uh One of the things I'm worried about is in the past. It hasn't been a great format for two-way collaboration like it's it's uh broadcast and the feedback from the audience is very difficult.

B

It's through like questions only so I don't know if we get what we expect but yeah, if we can think of something that works in that medium, I think that's a great idea.

A

Yeah, I was just um thinking we have like, like I don't know, yang and kishore, you guys could talk about uh like load, balancer, controller and kind of what what's going on there and nicole. If you want to have some slides about b2 or something like that, we can kind of all just talk about the future of where this is going.

D

um We need a new version last week, so and country is supports the aob and for nlp only support you'd import as targeting, and we plan.

A

Sorry I was specifically talking about talking about the load balancer controller in the talk, but an update. That's actually good uh too. So please continue with the update, actually yeah. It's fine.

A

A

Nicole, do you would you want to.

C

Oh yeah, sorry, I'm sorry so um yeah I think for now. I don't have like a good talk idea, but yeah. I can think about it, and maybe I can um give you uh some updates in the following meetings.

A

Yeah, it wouldn't be anything special like or you know, crazy or long or it would just be like you know, and we can. We can all write the slides together and just you know, this is what.

C

A

Like these are the things we've merged so far, this is what we're thinking about.

C

B

If I may, I think I think it's a really good idea, like we saw recently with the uh docker, whatever the docker deprecation truth is that, like you know the the headline spreads around the world before the truth can like put on its shoes or whatever. So if we can have a uh a a discussion of or a uh a talk about, what we're changing, which things are breaking and how like what you should do and why we're doing them?

B

I think that would be good so that when when, when it comes when we eventually have to say like v2 of the cloud provider and the headline is like every kubernetes cluster running universe is broken today like we can have like no here's.

C

B

You can hear exactly what is not broken and why we did it here.

A

Yeah, that's a good point.

D

B

A

uh I actually would be interested to hear the load bouncer controller update gang- if you do want to get into that.

D

So so currently we understand nlp will only support the instance ipmo, which is target import in the future. We will add support for the instance mode soon, so it will support, I mean, has the same functionality as our entry will be.

A

Got it so, are we going to? Is it going to be equivalent.

D

In the set of support annotations.

A

And will we be deprecating alongside the the launch of it and the load balancer controller? Will we be deprecating it in the cloud provider yeah.

D

I think that's the plan.

D

Okay, that allows us to move move quicker and they can share the same.

D

Implementation.

B

Yeah like with these, so I just want to say for the for the minutes, uh with the notes, we'll deprecate the low bouncer controller in the entry clip router and essentially move the functionality into the out of three ones. Right I want to like have the like. I feel like deprecating, the is the uh like removing sport for docker, and I want to be like. What's the what is the the plan for like people moving forward.

D

um We will support another type, called nlb influence, mostly so the intrigue entry code will still be there, but we want, I mean we want actively maintained so people will I mean if people want to try out the new notifier functionalities. They can.

D

I mean using the new aw new adventure controller, which is more updated.

B

uh So deprecate but not remove the load, balancer controller in the injector product in three cloud provider and uh investment.

D

B

Eventually be removed in the way to.

D

Other people either yeah. We want to remove it from the entry cover.

B

I think I think it'll be good to uh like do this talk and then we can finesse some other messaging around that and what we're actually what the plan is, but yeah I'll write that in a minute. Thank you. Sorry.

A

E

Be clear, the only thing about removing completely is like uh so far as it stands. uh The users have to install the load balancer controller separately.

E

It's like an action that the users need to take. So uh that is something that we ne. We might have to trade carefully, because if they don't install the controller, they will not have uh any load balancer provision, so that that is something that we need to work out.

A

I mean that's like you have to go, and you know this affects all aws clusters and uh removing load. Balancer support from the cloud provider is potentially a a hassle for users, so we want to definitely I think.

D

Yeah, it's it's not a depth case, so so I mean it's kind of a new little better time. So it's a new implementation.

A

Yeah, I'm just saying, like the since you're saying, like okay feature development will move um and I do like the plan of kind of you know deprecating, but not removing for uh the foreseeable future uh to not affect um just you know. Anyone who upgrades and and gets the you know a version of a cloud provider that doesn't have the balance or support. I think we want to be very, very thoughtful and careful before we did something like that.

B

um And we did it is, I think it's not considered a breaking change to um require additional components to be installed or like change. The flags like we do that all the time in kubernetes minor versions, like uh that's sort of an operator thing, I think the uh the compatibility guarantees apply more to the things that users see, um and so it's it's fine to require an additional controller. That's we shouldn't, do it like every minor release just for fun, but we we're gonna.

B

Do that, like as part of the externalization, I think that's absolutely fine, um but uh it's about what it's more. The bigger concern is what uh the end users see more than the operators see. We should make life acceptable for the operators, but the end users is really the thing we really have to be very, like don't break users type thing right.

A

Makes sense makes sense.

A

So we also have kind of on the on this. On on the deprecation topic, we have that pr or I opened a pr to copy the entry code legacy cloud provider over to the external and it's currently just waiting on the the 120 pull request to merge um and I think andrew added he has been adding some.

A

I I didn't take a close look at it, but I I believe that there's a check in prow now to um well. I think the first thing is that he added, I think it's himself and walter are the approvers on all legacy cloud providers, so the idea is features won't be merged there. Unless it's like you know, you provide a good argument so.

A

um Yeah, I I'm not sure exactly how this is gonna work, because, like there's gonna be there's, there's gonna be a slight gap here, where you know we're getting ramped up on the the external and um and like it seems like we've already sort of kind of frozen uh contributions to the legacy um yeah. So it's just a little bit more um motivation to to get the external working uh copy, the the legacy v1 into the external cloud provider, so that the source of truth is there and yeah. I think that's gonna happen pretty.

A

Soon, cool all right thoughts on that, I don't really have anything else to talk about.

C

Yeah, so uh I have up here for bumping: 2 is kubernetes 1.20, so this week uh the grenace 1.10 is live. So I I think my peer. I removed the working progress tag for my pr, so I think it's ready for merging. So I would like to get more eyes on that here. If people have time so so, like nyx pure merge, the relaxing part wider will be unblocked.

C

um Yeah yeah this one yeah.

A

Cool yeah: let's, let's see if we can get this merged I'll, give it another review today, yeah.

C

A

A

Shall I stop.

B

B

The only other item on our agenda is uh whether or not we have a meeting in two weeks.

B

On christmas day, yes exactly hmm so I think it's pretty clear that we are not going to have a meeting in two weeks, so our first our next meeting will be in a month like 28 days. I should say right: um I can't do the math seven, eight eight, maybe.

A

Yeah something around there, I don't I don't. I tend to avoid month, math.

B

Calendar says the eighth.

A

Okay, yeah, that sounds good.

A

First week back right so but it's friday, so I guess we can do it. We canceled the. I think we cancelled two of the sick, clap writer meetings, uh so the one that falls in the week of christmas and then the one after but.

A

I'm I'm fine with I'm.

B

We can always have the meaning if it's, if there's something on the agenda, because nothing has happened or if uh no intense, we can just wrap up early and see yeah.

B

A

All right anybody else have anything to add quickly before we stop recording.

A

Cool thanks for joining everybody.

B

Thanks for hosting nick thank you.