Kubernetes Event-Driven Autoscaling Standup, 5 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020-03-05 KEDA Standup

Description

Notes: https://hackmd.io/cEi_FerdQvyTvB1i-5U0kg

A

With this we're gonna go with it. Okay, so I just started the recording, we'll see. We only have a few items on the agenda, so maybe before we start and then we can do some quick updates and that way, I can mute. My mic, while other folks give anyone, maybe we'll just go around really quick based on the list here. We've all been on stand-ups before so I, don't know. If there's any updates, I know on red, you had to run last weeks as well. So if you have anything, you want to share yeah.

B

Just one couple of thing: one quick thing is about the release. So I had asked Satish to start the 1.3 release. I think we didn't get to it this week because of other things that are happening but I will I will remind him today as well.

B

Today morning he was not able to join because he had some emergency, but hopefully we will start it by today or definitely by tomorrow we should star and if the process goes, if the process is streamline now we might even be able to get the release out tomorrow by tomorrow evening, if not then very early next week, so so that's about the release other than that I don't have any other major updates. Just last time we wanted to talk about when Tom was here.

B

We wanted to talk about basically one of the things we have the instead of skip skirting around and not have a clear guidance around this governance of scalars and so, but but I said that it'll be better. If we have a larger group, including you and Emmett, and so I just wanted to bring it up that as we go and there lots of people, so there are a couple of access. This one is right now, as you know, scalars are included with Kira right. So do we want a model where it's not included with Kira?

B

And the second is that, should we have like a model where there are if somebody contributes a particular scalar, it's sort of tied in right.

B

If somebody contributes a scalar, are these owners and if there is an issue in that scaler, will they go and sort of look at it because they own it so the ownership of scalars itself, so those I think those of the couple of things but I'm sure they add more so so that's just one thing: I wanted to flag that we should start thinking about and we may well decide that hey.

B

This is a very clean model and we just want to include it, and so it's Kira is like comes with batteries included, like everything is included, don't have to worry about installing scalars from outside, but we have to tackle it explicitly at some point. So.

A

Make sense make sense, I.

B

A

Makes sense, I have some thoughts, but I will circle back on that one and I'll see if I'd how everyone else is thinking about it too, that helps hundred thanks, yeah. That's it Sandra anything anything from your side and apologies. I know, I missed. Last week's and I'm I was spending a little bit of time trying to catch up on on issues. I, don't know if there's anything top of mind from your side.

C

A

And sip your neck I know we sinks briefly on Tuesday I, don't know if you have anything from there.

D

No, no just what's on the agenda, so nothing good! Yes,.

A

And it's mostly uh I I think what you've been doing you mentioned in Tuesday's, some of the duck typing design, duck typing work, yeah.

D

Yeah there's a thing: I'm I want to focus now so I have sometimes so that's related to my like to the proposed agenda on the branch on the github, so basically I sweep.

A

D

A

So this yeah I wondered if tompa this one. We could jump straight to this. One I think this makes a lot of sense honestly to spin up the v2 branch, because all the duck typing I think would go under that 2 dot, X release yeah yeah. So so it's.

D

It's more about like the the core will be a little bit rewritten, so I think it would make sense to create other like the dead branch for double and it shouldn't effects. Chaos at the moment, I think so. So, basically, if there is a request to to the master branch, we can clone it to the to do. A developer branch, as well like to include include the latest changes on the scalars. If we don't want to change those scalars, somehow or I mean like the signature or whatever.

A

Yeah I, don't think so I'm trying to remember I wonder if we even have like a label for breaking or something like I I, don't I think the only thing that we've really flagged that would be changing between v1 and v2 is the duck typing. Maybe it was. It was maybe in delivery to release or something like that. Oh sure. Yes, that's a good one yeah, because we have this this one yeah yeah yeah yeah. So it's duck typing! Oh, it was the we.

D

A

To the net this namespace yeah.

D

I will increase as well in the into the into the change so right this is related, so that does the main. Basically, this the main reason why I wanted to keep the separate branch, because you know there will be different. Crt is okay.

A

Cool yeah and if you have, if you need any help with that on read, you have any concerns with us. Spinning up a v2 branch on on the repo.

B

Totally make sense, that's the right way to do it. Oh great.

A

Awesome so I'll just go through the rest of this quickly, then so for the CNC F is in mentioned in the agenda, so Michelle Nirali just this morning, agreed to sponsor kada into the CNC F Liz Rice had agreed earlier last week, so we have two sponsors we have. One left I actually was messaging William from Red Hat today, because he mentioned he might be able to help pull in the third one. So I think we're in the final stretch.

A

Now we just need to get that last sponsor and it looks like we might need artwork, which I'm just looking at this now as my kitchen gets destroyed behind me. Let me see I think we already have like we have the icons in the repo, so I don't know if we need anything else other than assets we already have so.

A

Okay, so that's that one! This is a good one, because I like over the last few weeks too, is we've kind of made progress. The stand-ups have been more short for one, but I'm also wondering we talked ages ago about maybe moving these to every two weeks and at a time there were still like whatever ten people joining every week, so we're like, let's keep it going, but we're visited later. So this is just any thoughts on.

A

Should we either just keep them kind of short and quick, and maybe we'll just do like 15 30 minute stand-ups and keep it every week. Should we move it to every two weeks every month, I don't know if I call has an opinion on red I, just.

B

Have a quick urban, like kind of a green now just to the point that we just making that I think weekly seems and and just just looking at I think exactly what he said that we don't have so many updates. Every week fewer people are coming in the same people do not coming in every week and and and so except I guess. Sandra Sandra has been really sandra me and you for most part, but otherwise, like most people are coming in every two weeks as it is right.

B

So so so so my two senses, yes I, think it makes sense to have it every two weeks and and and for now we can still keep it at 45 minutes for every two weeks. If you think that's also too much, then we can reduce it to thirty minutes every two weeks. So that's.

A

What I feel like sense, Sandra and say beinac I'd, be curious if either of you have a thought because I know like sapien axis is kind of our primary touch point for some of the work you're doing I, don't know if you prefer shorter weekly one sorry.

D

Yeah, this is this yes, so it is. This item was written by me in the agenda because I think that or I concur on what we said. I think that we don't have that much changes recently. So we can change to bi-weekly and even like I. Think then that the shorter meeting will keep the people try to focus on the things and not you know not spend too much time so so, I'm I'm okay with this yeah.

C

I preferred bi-weekly meetings as well.

A

Great, so we have a unanimous quorum of four folks, but that's perfect. Okay, so all I'll reach out to Tom and let him know I think this is good, we'll probably plan on just doing that right away. So we'll have our next meeting be on the 26th of March and then we'll move to bi-weekly from there and see how that goes, and we can always adjust as needed.

C

You might want to add a not a section for the 26, because was it 19th to talk about the government's because he won't be able to join in to them. I.

A

See, okay, yeah I'll reach out to Tom and see what he wants to do: oh yeah. This is where he want to do the governance, you're right, you're, right, okay, yep thank.

D

You so we could we can. We can meet next week and then start the week reschedule yeah.

B

Yeah, that's fair. We should just see what is availabilities and, as you said so uh one quick thing since we're talking about since we're talking about having a kind of changing the schedule for the meetings should we also talk about I. Just noticed, like a native, has like a scheduled release where they do it every six weeks. So do we want to go something like that? Like whatever happens, like tick tock, you just say a every three weeks every four weeks the next release is going I.

D

Think it's good idea because I know there were some discuss discussions on the recent scares so.

B

That there's no confusion. We just say that this is what it is and and we are and right now it's mostly people from within Microsoft, doing it like a mother and Satish have done it, but we can have a release owner and we can even share those responsibilities between different people for the next sillies. Have it once in four weeks or three weeks, whatever it makes sense and just make it a little bit more formal. It's just.

D

Yeah I think it's good for users, because then they do know what we expect exactly.

B

That's exactly right, so they know that okay, this release is coming so on and.

C

It also makes a release process a bit more open source community as well. It's pretty cool, yes,.

B

Exactly right, like I would I would it would be awesome if, like zib, Nick or Sandra, if you could be the next Lisa notes and so on and so on, and so and we can make it completely open. Yeah.

A

Makes them make sense, yeah I, think I think that works I, like part of me, wants I liked. Initially I wondered like is six weeks the right one too, but there's the other part where I want to balance like someone gets a PR, merge and I want to get the docs up and kind of like heaven and and I'm wondering like once every three weeks there's also the risk to that. If nothing solid has been popped in within a three week period, there are pretty light releases, but maybe that's okay, too I think that's okay.

A

We should just like.

B

But but I think the regularity and and the fact that people can depend on having a particular schedule, actually helps a lot. I feel and.

A

You have a preference on, or around time span, like three weeks four weeks, five weeks six weeks, I think.

B

They have reached a stage where, once in four weeks, sounds okay, but that just that's not there, any scientific analysis delivered and just.

B

Once a month like monthly release,.

C

A

A really good idea, that's very good yeah yeah.

B

Yeah, that's that's a good point. Yeah.

A

That's that's true: okay, I I think we should go with that, so starting probably starting with 1.4. So maybe honored we'll look, so we might still do the weekly next week for Tom I. Think we'll probably plan on that. Just so no one has to whatever worry about it too much and then maybe we'll plan. The 1.4 release would be four weeks after March, 19th, yeah, I, think and.

C

Then we'll just kind of go on the every.

A

Other week, cadence from there yeah.

C

19 is actually two weeks from now, so that bi-weekly I see.

A

You're right yeah, so when Tom created this Irwin who yeah he actually did yes, so we could actually switch to bi-weekly now and then do I still yeah. Maybe we'll still just do the release four weeks after this one, so they do lineup and so 1.4 would be on whatever four weeks after March, 9th or I. Guess four weeks from today, that's the two choices on red. Do we want to do one four weeks from today or four weeks from March 19th.

B

Let's see when we get this release first point.

C

B

The one point three: for some reason: if people are not available, and so not it takes more time, then we'll figure it out based on that yeah.

A

It would put us on April, 2nd, potentially pretty, actually yeah, okay. This is actually really good. I think these are actually really good changes to help add some more consistency and and encourage involvement too. So it doesn't feel too ad-hoc great awesome, very good topics on governance, then so so that's the the last thing on my thinking here on erode and I know. Tom. Has this issues and I'm curious, my initial thinking before I open this issue was gonna, be for governance.

A

I could take a stab at opening a pull request, maybe on the dock site, which just kind of describes and defines our governance, I think I've kind of vocalized it not too concretely in the past and and so the thinking is kind of just like hey. This is what comes out of the box. This is how you should think about creating new scalers. This is what those different taught like. If you see something as community sponsored or company, sponsored here's the difference to that.

A

So just just defining some of that. Some of what tom has here as well. He might go a little bit like how do we manage access to our docker hub account, I, guess yeah, if it's a if it's a commute like if it's this durable task, docker thing, which is a good one? Oh so maybe so maybe the X item, though, is I. Think I could take a stab before our next meeting and I'll tag. Tom on this we're pretty much.

A

I am inconel proposal to go with, and so maybe on the 19th plan on having the proposal and we'll really just discuss it. I'll try to have the PR open ahead of time, so folks can review it, and then we can all just either give a thumbs up or a thumbs down or or say.

A

We need to make some more concrete changes before we merge that in tongues, good, okay cool, you have to take a stab at writing governance proposal to go on to the doc site and wait okay, great any other topics before we want to wrap up.

B

Yes, so, okay, so for the further for the just further just confirming for the CN CF sandbox. So the only thing they left is just one more person saying one more per TOC member actually including order willing to sponsor that's it right and then B then, and then we are in sandbox as.

A

Far as I know, yeah like once once we get that third vote, I don't know if we have to like wait for them to actually have a meeting to give their thumbs up, but as far as I understand it, you had to give that last vote and we're done. Okay, yep long journey dear.

B

Do you know just one last question: do you know if the Alexander or somebody they were working on, including Keira and Kay native, did that get marched? Is it Angeline.

D

B

I'm just curious.

D

It's still still like working progress, but it is going is going forward. They basically add like or discussing crud, to write annotations for tea native, so they can annotate annotate the objects on cognitive and it will basically fill the necessary options to the scaled object for a for a que. Dice que voce. So, okay, I can't I can't.

C

D

Can't I can send a send an issue or the poor request number just yeah.

B

I was just curious that yeah.

D

B

That went through and and if we can now sort of say that yeah you need to use the scanner they.

D

Are starting with the bitter Kafka source at first because they have several like, though yeah even sources, basically the same thing as scalars. Yes,.

C

D

Starting with a Kafka source, and once it's in they will basically do the rest thing for the other other open sources, yeah I got the issue number, so I will put it in the chat.

A

Perfect and I like that in and it looks like tom, is haunting our notes from from far away.

A

Well, great: okay, thanks thanks Jeff yeah.

B

Thanks everyone for joining.

A

We'll plan again on march 19th, being the next meeting I'll just make sure on slack and Twitter and and even the Google Calendar I'll try to open a pull request today, then so that everyone knows that that's the change I'll, probably even honestly. Next week, I'll probably just join and make my screen share and be like it's happening next week, but I'll sort that all out I think that's that's easy enough!

A

So I just sit here, kids are going to school, yeah, they're, they're, all fine in school, honestly, I think kids are low-risk enough with the coronavirus stuff.

C

A

Think they'll be good, so I just lets me work from home, which has been fine honestly. Why I, actually I'm able to focus a lot when I work from home, cuz I? Don't get kind of people asking me side questions so has.

B

A

Yeah yeah, okay, cool great thanks. Everyone stay safe.

C

A

We'll talk to everyone in two weeks like see ya. Thank you. Boys.