Kubernetes Event-Driven Autoscaling Standup, 3 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: KEDA Community Standup - 2020-09-03

Description

Meeting agenda and notes: https://hackmd.io/cEi_FerdQvyTvB1i-5U0kg

A

Hey everyone how's it going sorry about that. My uh my daughter, zoom uh got locked out for her school, so I had to go figure out what her username and password was again. uh Let me go ahead and open this.

A

We can go through any agenda items that we.

A

Have I'll just share.

A

This screen all right here we go.

A

uh Let me open up this to make sure I can see who's on the call too great uh all familiar faces. Welcome everyone. um Let me go through and make sure tom's done this.

A

uh I don't see tom on the call, and so maybe I'll just ask. I don't know if everyone's looking at this agenda as well already I'll paste a link in the chat in case you don't have it, but mostly an open call, maybe just paste into chat. If there's something you want to talk about, that's not already on the agenda, but maybe I'll just go through the agenda here. The only one I know of is, I know.

A

Ahmed did some work opened a pr on docs and I believe on the keto repo itself around oh yeah. It looks like that's on the agenda, so, okay, um so tom has a question on if anyone's had issues with hackmd I have not, but maybe others have has anyone else had an issue with this hackmd tool where we do like this collaborative markdown thing.

B

Sometimes it's uh lucky for me as well, but.

A

Okay, I'm fine.

B

If we move to google.

A

Docs, I'm fine. If we keep it here, I don't really care a whole lot. I personally like markdown a lot, which is why I chose this over google docs, but I have zero preference either way um so yeah. I I don't really care, maybe I'll just add in the notes. I'll say we discuss the google like. If, if he wants to move it, he can move it. I don't think anyone will miss it or be sad. If it's moved um uh sounds good, oh yeah, it looks like mine's lagging a bit right now, that's funny!

A

This is the first time I've noticed this.

C

Slow for me as well.

A

A

We're cool with google docs, okay, um so on the metadata one I pinged ahmed about this, I didn't actually look at all the pull requests, but I know he went through. He reviewed all the issues or all the metadata properties that we're loading in from an environment variable, I believe, maybe there's the pr in this link here too uh yeah.

B

The pr is over there, it's still open, okay,.

A

It's on the open side, yeah yeah, uh all right, add vn right there uh I see yep, so he took all of the ones that are pulling in from an environment variable or secret, and he appended from and on the end of them, um and so that now it's more clear from the pattern of like. Should this be a literal value, or are you pulling this in from an environment or or secret?

A

um So it looks like there's a few comments here. Maybe this.

B

It's just it's just the formatting issue, so yeah, the rest of the pr is looking good for me. So if anybody wants to look at it, but for me once the once the formatting is fixed, we can we can merge it cool.

A

Great any other thoughts on this item. I know we spent a bit talking about this last week, um but this looks this looks good to me. Yeah, sweet, uh sweet, so I'll pop in just need to clean up formatting on the.

A

Next one here helm2, oh yeah, this is one of tom's favorite issues. I wish he was on the call for some of these, so he could give his uh two cents. I imagine he wants to remove support for our helm2 helm chart so.

C

I actually have a pr in in the helmet I'm charge 60 and it would it probably didn't make this obvious enough, but this it's, I updated the chart to be helm2 and helm3 compatible.

C

I put it as if uh this should allow for these both helmets and home three. So what this is doing is it takes the crds that would typically be in the templates uh which helped so help to use the templates directory of crds and use annotations to install the crds helm. Three does not do that. That's where.

D

C

Problem comes in so what the? What the uh workaround is, this you just went right past. It is this templates uh crd.yaml which references the crd directory, so this should allow for both helm to I.

A

See great makes sense.

A

Yeah, it looks like there's just some conversation around this, but it sounds like yeah, because I let me see if tom was saying anything else with. I think we should stop supporting it, so we can fix yeah. So tom tom wants to get rid of the issue, which is people think it's broken when they install with helm3, because it says whatever unsupported crd installs, something something it sounds like.

A

uh If I'm getting this right, travis you, you might have a pr that resolves the underlying issue, while still not necessarily making it so that we have to deprecate support for v2. We could still support two and three and we would still correct that issue. 18. yep yep, that's great yeah! That's my preference!

A

I I mean I don't know how many people are still using helm2, how much it matters, but given that it there might just be this kind of nice way where we load in the templates directory with this crd file, which I don't know if you pulled this from other projects or if you're, just uh smart enough with helm to know this was possible.

C

So I'm not that smart! This was a. I noticed this actually in um we works flagger yeah.

A

C

This has been a problem because we use helm2.

A

C

And helm3, so I've had to deal with this issue. That's.

A

Great yeah, it makes sense that this is like we're not the only project, that's probably in the spot of of having crds so yeah. My preference would be, and I don't know how much is in this conversation uh it might have to do more with the versioning. If we move to the 2o uh in this thing, or if this is a one dot x thing, yeah.

C

I mean I could possibly break this pr out into two different things. Maybe that would be better. I'm.

A

I'm okay! If this change, I I mean, I guess I don't. I don't actually know like, and what I was going to say is I'm okay. If this change is bundled with uh here's, how you install cada 2.0 in a helm, chart thing which it looks like is something you've grabbed in here too, and I'm guessing you're updating the crds to have the right definition for k to two um and so more or less when you start installing k-2, which should be the default here in the next few weeks.

A

You would get this behavior, I'm okay. If we do that, but there is the like. I guess I haven't actually given much thought into what happens with k to 1.0 helm charts um when we have 2.0 are we do we need to? I know, helm has a versioning thing. I guess I don't know how thoughtful we need to be on. Like does our charts repo, just at one point switch to 201?

A

If you want to do one o, then you have to manually pull in one of those older versions that we've stored or do we have to have both active always in.

C

The chart email there is an app version uh field, that's supposed to correspond to.

A

Yeah yeah this one right here right and then, and I think, when we're saving them like when we run this command, um that we're actually like it's grabbing all the previous versions as well, um that we publish to our whatever github page um good like I can go in today and I can still use helm and, I could say, use chart version 1.4 and it will actually work on this repo. uh I think so. Yes,.

C

A

C

Yeah that would make sense to update both oh.

A

Yeah you're right here, yep, so here's all the here's, all the zip files that we're exposing right now from our from our repo and I assume, they're all indexed as well: yep, uh okay, so yeah. I guess we might have uh decata2.x versions of the chart in k201.x how exactly we handle that from a repo structure.

A

uh I don't know because, like your pr is just changing the the underlying ones, so like master more or less like the default, would change to 2x, which I think is fine like I don't like. I don't think we really plan on having a 1.6 release. I guess we might uh anyway. I don't know if anyone else has any thoughts, I'm kind of just rambling at this point as I'm mentally trying to piece this together.

A

Travis fix the pending closure on when, if 2.x charts get published.

A

Okay, yeah, uh I I think travis I'd almost just kind of leave it up to you and maybe the folks on the pr.

A

If, if you want to break this apart- and you know, have a version of the chart which uses k to 1 5 and just gets rid of this issue so that even if somebody does want to use k210, this gets rid of I'm cool and we honestly need- and I assume this is part of the reason you did this too- we need charts for v2, um like I've been using xibianix make uh file which works great, but a good chunk of folks will want to use helm as well.

A

um So we will need two dot x, charts out, uh I'm cool. If this is the thing that gets two dialects charts and closes this issue all in the same thing personally, but whatever other folks can can chime in on that as well: okay, okay, um okay, so that's the helm, one!

A

Oh okay, dockers policy, limiting image retention, an announcement for github container registry; I'm just going to read this really quick, and then I don't know if anyone else has context. Docker hub is applying throttling on polls and automatically moving image tags that are no longer used.

A

Okay, so we probably have some older images that aren't being used very much github container registry is trying to step in and say, hey we'll, be your friendly docker hub, and so I guess the question is: do we move over to github container registry because of the docker hub stuff um and tom saying? Maybe some of the reasons is that we might get better metrics like right? Now we have the top level how many polls we have, but it just says whatever like 100k, we don't really know what that means.

A

So maybe there's more metrics there. I don't actually know much about github registry and uh yeah. Obviously there would be work to modify our github actions in the ci cd process to publish to github. Does anyone have any thoughts here on this one? I I didn't know about docker hub's new policies. I don't know if they're impacting us yet or if it's just something that could impact us um yeah. Does anyone have any thoughts on this whole container registry thing.

E

I also heard that jeff that I think after uh that, they're also starting to charge now uh uh and- and so there are some there's a premium plan. Also uh after you reach a certain uh limit of downloads, that's.

A

Probably what I mean.

E

Yeah yeah, so so maybe we so either. So that's the two options I think either we should just get a paid account. I mean it's not much. I think it's some ten dollars a month or something but.

A

Yeah, it sounds like docker really wants github container registry to be successful here.

E

Maybe maybe this is the partnership that they're doing with microsoft. I don't know, that's we'll start charging so that, but I don't think github container registry is free either. I am not sure actually.

A

uh Oh sure, because I know they are they're still figuring out their whole pricing model. Stuff yeah, like I'm, I'm sure through the cncf, we could probably get a pro docker hub account uh with part of that, like cncf perk stuff. So I I'm less worried about the money aspect, but I I don't know like yeah. There is a part yeah. I don't know. I don't know on this one. Maybe we it's something that we're all aware of now.

A

Maybe I'm sure that there's a conversation, that's got to be happening on like cncf maintainers boards, because again this is something that we're probably not the only project, that's going to be a part of, and then in fact, there's probably other projects that already have crossed whatever. That threshold is for downloads that are in the cncf.

D

A

Don't have to figure out what to do uh so, maybe for the next step here um I can send an email to our cncf rep and try to understand if there's any precedence here on what other projects are going to do and and we could kind of just follow it's a good idea.

A

Yeah, that's I I I'm more. This issue is more interesting to me from a docker strategy, but who knows I mean I mean that I'm tangenting, but everybody's always wondered what docker's revenue model is going to be, and I just loved having docker hub and it's sad if they're gonna try to make money from it, but it makes sense. The world runs on people making money somewhere.

A

uh Okay, next one is from tom. I think it's just saying like hey oktoberfist is coming up, it's a big spot where people go contribute to the first project. I think this is a good call out, um and it's mostly like is there anything we could do on our repo to make it a very attractive place for people to come on hacktoberfest uh and start to contribute something? I know.

E

It's like uh is this like a cncf kind of thing or.

A

It's just like uh open source community twitter thing where people are like hey, go, contribute to a project because it's october um in the same way it's like serverless september this month. I know we had the I used to do a better job at this as well like we have our help wanted or good first issue yeah. It looks like there's actually a few of these. uh Oh and it looks like tom's actually gone through an added hacktoberfest. So maybe the issue here is more like.

A

Should we create an actual document that people could go to um that maybe says like hey? This is where keda is go. You look at these filters for hacktoberfest.

E

Maybe you want to just put it on the just kind of a banner on the home page of keda dot sh. That's not a bad idea!.

A

B

E

A

B

I guess that uh the note from tom is as well about like going through the issues and maybe mark mark those like which are good for for oktoberfest, like.

A

Yeah he's got a few here, but going through and like there's, probably older ones like these are all all the ones he marked are within the last week. So there's probably ones that, are you know deeper down. I'd actually be good candidates as well yeah yeah. These.

B

Ones are new, they are uh recommended by tomasz who did who did some some stuff on on on this on this side, so.

A

Oh great yeah, so thomas yeah, maybe you even went through and added these labels. uh Oh yeah zibinek. You did as well, okay yeah. This is, uh I think, that's a good call to action for everyone. I know there's a few here, uh the dashboards another one that I'm sure I would love if somebody's feeling very ambitious in hacktoberfest, and so maybe this is just kind of like a group action item to mark uh items with hectoberfest.

A

Good first issue wanted uh and then I am curious on the banner thing I'll just take note of it right now, I'm not going to sign up for this just yet, uh but I'll mention.

A

uh Maybe we could put a banner on the dot sh site that points to us.

D

Yeah- and there is an interesting page from github, which is the contribute page which points new users to the good first issues, also and and the contributing md or anything. It's like that. I posted in it in the chat. So if.

A

You want to yeah. It always takes me ages to find this one. Oh yeah, nice great yeah, so they even have this view yeah, so yeah it honestly. We could even potentially have a banner that more or less just links you to this page. You've got the contributing guidelines and then you've got some good first issues: um okay, yeah.

A

We all right, it's a good call out yeah I forgot hacktoberfest was coming because this entire year has been just one massive single day, tom thought of it and the rest of you. I could see.

A

Labels are being added by many of you, uh okay, so I reached out to the person who did the original lightning bolt and he deferred for a few weeks uh I poked someone else who I know was in the design space to see if they could add the lightning bolt, and I did not hear back um I I wish I had photoshop, because at this point I would almost just take the shot of doing it myself.

A

um But it's still, I don't have any progress here, at least from the the ones that I poked. I think really it's the here's, the the the if I open this up um like this, is the extra bolt ex uh emphasis that they added with like the blue shadow. This is legit the only difference because the logo we have uh it's like the cut out of the a is that shape, but you don't actually see the lightning bolt. We don't have this in svg. We only have it in png, um so I'll. Try again.

A

I actually have a call with the person who deferred tonight at 10 pm. I forgot about that because he's in australia, maybe I'll poke him and I'll say like hey, since I'm going to do this presentation for you, maybe while I'm presenting you can just find this file and save it as this sfg.

A

But but yes, there will be no response.

D

I can help you with that. One.

A

I'm more than happy to ask if you've got yeah whatever, whether it's or photoshop or illustrator, we have the we have svgs for the normal icon like this one. We just don't have you'll see you'll, see here. Oh, I guess, there's another svg in here. It's just really adding some white emphasis with a blue shadow.

A

uh Anyone who has moderate a graphics ability we'll probably be able to pull it off um so yes uh go for it, take a shot. Oh yeah! This is the one here's the svg. This is the. This is the source that we just need to modify so godspeed tomas. I have full confidence in you, uh so I will say: jeff will poke ingest the person who needed a few weeks before tweeting.

A

Okay, sweet, uh oh yeah! uh This is a good reminder. Let me look at what the zoom uh waiting room policy is right. Now they keep punting this date. Okay, so it says september 27th, which is uh coming up in four weeks, that every meeting will need a passcode so yeah. I need to add a passcode to this one um yeah. The only thing I keep hesitating on is how I do the passcode, without without people getting stuck and not knowing where to go, uh but it's okay. I wonder maybe what I'll do is.

A

I can create a new meeting series with a new kind of like room thing, because we're already gonna have to add a password anyway, maybe not maybe I'll just add a password to this one. It's more just the logistics, maybe I'll just add a password and I'll do a push to cata.sh, which has our community stuff. So this is more a heads up to all of you who are joining now and I think I can do a world where I had a password and a waiting room.

A

I don't know I would love for there to be this world where somebody's trying to figure out how to join- and I can say like hey by the way we added a password to make uh to make zoom happy um because yeah pretty much I'll, just add a password here. I'll change the link, so it embeds the password in the url and then I'll just say like the password is whatever uh you know, event driven uh something silly like that: it'll probably actually be event driven will be the password.

A

um So hey, if you get prompted for a password. If you try to join in two weeks, come here to look at what the password is, I will plan on making the password event driven. uh I will update this. I will update the google agenda and I will post to slack and on twitter, so heads up that's coming because if we don't do it, then zoom's gonna get upset and start canceling this meeting anyway.

A

Any other thoughts on on zoom security jeff will add a password this week.

A

uh Yeah- and this is just tom wishing that somebody will pick up this item, um which I don't think anyone on this call will necessarily pick it up, but it's could we add uh um whatever we should add. You know what we should add here.

A

uh Some labels like good, first issue and hacktoberfest, because I believe this is really just pulling in an updated version of the event hubs sdk and following the same pattern that we've done with other azure active directory, pod identity, uh things but yeah, I don't think anyone's going to sign up for it who's on this call right now, uh honor. This is more of an fyi for if, if like, uh what's this uh yeah or uh yoshi wants to appreciate.

E

That they can't do, I think the question is like with anything is uh uh how much of uh do we have somebody who really wants to use? It is blocked.

A

Yeah, I know yeah. As far as I know, this is the only I haven't had anyone email me like. Obviously, that's not necessarily what happened but like there's, no microsoft, customers. I know who have emailed me and said they need this tom. Obviously,.

E

A

E

Anybody who's using.

A

E

So uh it's fair, uh I think prioritization-wise.

A

I like getting 2.0 out the door and everything finished is like the big, bigger thing, but I think at this point once this pr gets merged. uh I think it's really just more of a messaging thing for us. I I think from a 2.0, and maybe this is a good place to pause, to make sure I capture it, but uh I think most of the 2.0 work is is completing and- and now we just need to merge in like this and a few.

D

B

A

Make the push yes from from my.

B

Opponent like basically like, if we, if we merge this these prs and uh what else in the home chart, then we are good to release the v2. So I was thinking about uh releasing the beta next week. Yeah, probably because tomorrow is friday, which is not a good day for release. So so probably if we merge those those pr's, we are good to go to release the vita next week or monday or tuesday.

B

uh The only only only thing that's missing is um is the migration guide uh for ford scale. Jobs. Oh, is that still pending yeah yeah, I I I was trying to ping sushi or not slack, but I haven't heard from him so.

A

Is he out uh on road? I haven't talked to him very recently, but um no.

E

No, no he's here he's here he's here he's just working on the hackathon this week, but uh but uh can you repeat that zebra nick, I was just distracted for a second.

B

uh Like it's, it's like the finishing the migration guide and maybe like maybe another one minor like documentation issue, so maybe if he, if he can like uh like ping me on slack, I can. I can like give him like the recorder.

E

B

E

Yeah, I I will send him. I will send him a message immediately.

A

Yeah yeah more or less in I'm, showing it here like the what what sibyanic did for deployments is. It was like: hey, here's, just a bullet point of all the changes that we made and here's what like scale, jobs expect in v1 and here's now what it looks like in v2 or scaled object. I mean uh which is super helpful for me, like honestly, when I've been doing the migration, uh because I haven't been running the script yet that travis had done, uh which I still need to do.

A

I pretty much just come in here, I'm like, oh, okay, I'm gonna change, this property, I'm gonna remove this line and I'm gonna change this property and then I'm v2 compliant. So, ideally somebody would have the same thing. So it really is it's just the bullet points and then a sample of v2. It looks like we already have the sample for v1 with the comments and I think we're good.

C

It'd be good to add uh ahmed's or a mouse.

A

Oh yeah, his uh table. Yes,.

C

A

True, we do need to map those broken properties now that he added in the in that pr yeah yeah. That's a good point.

B

Migration guide.

B

Do we want to have a home chart for for the beta release.

A

uh I'm okay! If we only have the the the maker make file that you have right now, but or.

B

Like or don't make file like can produce like a one one yaml file, which is like huge long, huge yaml file, which is just one file and user, can just apply this one.

A

So sure, rather than necessary, having make but the the only one is like since I know travis you have that existing pr like if we get that merged in this week, even better if helm's there, but I wouldn't necessarily- I guess what I'm saying is. I don't think we need to block on helm if it's there, that's great.

B

A

B

Agree so if everything goes well like with the with the pr's, uh I think that some on tuesday, or something like that, I will do the release. I will sing with tom.

B

I guess that everything is is ready.

A

It'll be awesome, uh I'll make sure to turn on all my slack notifications, but I can up with that as well. I guess I'm out on tuesday, um but so, if we actually want me to help push anything or whatever I know tom, mostly out of the box, so don't block on me, but uh I I can block some time next week get up with this too uh and sorry on this event hubs one. I know I I started rambling tomas.

A

I think you might actually have been chiming in on something I just wanna make sure I give folks if anyone else had thoughts on this pod identity event, hubs thing.

A

Okay, cool, mostly just trying to make sure I didn't give anyone out the chance all right. So that's how the agenda items. I think this v2 list is good and this, in my mind, is the top priority. Obviously, I've got to do the zoom thing, because I don't want zoom to shut us down. I can send that email to the cncf we'll see what happens with the logo, mostly just kind of figuring out what to do with these pr's and then maybe we'll move to google docs.

A

At the same time, we move to a password, zoom meeting, who knows anything else uh around v2 in general, keda in general that anyone wants to bring up or chat about while we're all here.

D

I just wanted to uh I'd want to thank to the good first issue and the hacktoberfest idea that uh I think that's not only. We should review the current issues, but if we want to mark them with good first issue, we should provide useful description.

D

We we should help people to onboard and understand what have to be done in the issue, not only at the label, uh because otherwise people will not pick up those issues because they can be hard.

A

It's a good one. Yeah like I can even go through on the event hubs, one I just did and more or less the sentence I rambled off of like this is what somebody would need to do more or less just capturing that in the issue, so that if somebody does see it they're like oh okay, I need to go. You know, check out the event, hubsco sdk and do the same thing. They did in these lines of code on the service bus one uh and then this one's done, but yeah that'd be great.

A

If we can uh uh make sure we add useful descriptions and all these, so it's it's really easy to know exactly what's being asked.

D

Yes- and this really helps because, for example, in apache airport, when I'm the the maintainer, uh we have a lot of good fierce issues with good descriptions and people are fighting to pick up those issues and that's awesome.

A

Yeah, that's a really good call out. That's a very, very good call out.

A

That's great yeah I'll go through some of those and and for the ones that I'm familiar with, because I know a few of those. I have added the label for make sure that I I specify more of that uh great awesome. Anything else: sweet. Okay, thanks everyone, we've got a, hopefully a a pretty big week next week, then, with this alpha release or beta release, um I I'm even fine if we call it release candidate release each of those have different connotations of quality.

A

uh I've been using k2o, happily for the last month, and so far it's been great, though granted I mostly use it for demos and presentations and not production workloads, but still the demos have all been flawless. So thanks, everyone and uh we'll chat again in two weeks in a password-protected zoom meeting awesome. Thank you. Thank you.

D

A

See you everyone.