Kubernetes Event-Driven Autoscaling Standup, 15 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020-15-10 KEDA Standup

Description

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

A

Hey all sorry about that uh honor deny where a customer called it. We were trying to wrap up quickly but didn't want to close too shortly. I see the recording has started. I I don't mean to interrupt. If we were started uh tom, anyone did we did we start anything or should we just get going.

A

We are good to go. We are good to start yeah, okay,.

B

We're ready for you guys.

C

All right uh thank.

A

You and I'm seeing okay, I was hoping aaron was actually gonna join this, but maybe I'll give a side update on his stuff uh all right. Let me open up the agenda and share my screen and we will get right into it. uh Apologies again, it's been a a hectic morning for better for worse.

A

All right here we go share screen.

A

Oh, I think I'm sharing nope just that window, perfect.

A

Okay, all right! So we have the agenda. Oh yeah. This is actually media agenda, uh so welcome everyone, uh since we're a little late. I still actually want to give the chance, because I do see some names here- that I don't recognize as well. So maybe we'll do very brief introductions in onrid and ahmed uh and su yoshi don't feel offended. But for the sake of time, I'm going to introduce you all for you.

A

So I'm jeff, I'm one of the maintainers for cada program manager on the azure serverless team, uh and we have a few other folks from microsoft as well, who are all involved in help with decatur project, there's ahmed al-saeed, honor, guard and suyoshi. So those four of us were on pretty regularly uh so let's go through and just make sure the rest are there. I see tom is connecting to audio still. So I'm just gonna call out folks on the list. I see them. uh Richard copen, you wanna, do a quick intro.

D

Hi everyone thank you. Jeff preshow, that my name's richard coppin, I'm the developer experience lead for ibm, mq, I'd like to introduce you to jess and callum who also on the line uh over the last few weeks, we've been sort of looking at cada, jess and and kind of joined us as new graduate hires and they've, been looking at cada with a small team and have put together a candidate scaler for ibm nq we'd love to share that with you really excited what we've done.

D

I'd love to get some feedback and and see how we can work together.

A

Awesome, that's great um yeah. Let me make sure to add this. I might add it above merge uh ibm. It was ibm mq right that the scalar was for right.

D

A

That's cool we've.

D

Made it above the merch.

A

Yes, yes as important as the merch is, though, as you can see here uh these. These are the critical questions uh awesome well. Thank you all so much for joining uh shubham I'll. Let you go next.

E

Hello, everybody I'm from.

F

E

uh We are working, we are working on keda as anti as a poc project and we will contribute in future.

A

Awesome great well, thank you so much for joining us. It's great to have you here, uh zibianek I'll! Let you go next.

B

Hi everyone, my name is biniak, I'm an engineer from red hat serverless team: I'm maintenance as well.

A

Yes- uh and I got an email the other day asking if I wanted to nominate incredible people in the cncf civilian neck and I'm not gonna lie that your name was the first one that came up uh so we'll see what happens. Maybe tom can nominate you as well and you can get some nice recognition so uh an understatement uh introduction uh jess callum. I know you kind of got uh pseudo introduced by richard. If anything else you want to add, or we get to just jump into the agenda.

C

No wait: that's cool um we're good to go ahead.

A

Hello great to have you here and tom. I know your audio's working now, uh oh and tom tom I'll. Let you introduce yourself now that your audio does seem to be working.

A

Maybe it's not well I'll. Introduce tom uh tom works at codeit. uh He is also a maintainer, uh does quite a bit for cada and open source in general. He has some other open source projects too. Okay, uh oh yep tom! Are you there yeah? Sorry?

A

Is there a lot of noise for you? Oh, it just sounds like you're on speakerphone, but it's fine. We can hear you now.

G

A

You good oh yeah, okay, uh just making sure all right. I don't know if you had anything to say, but it sounds like you're. Just letting us know your audience.

G

No, no, no! I'm on the phone, because I'm on a company event, sorry.

A

Oh no worries wow see. This is why tom is is amazing. Dedication tom, we bumped your merch down a little bit because we're going to talk some about ibm mq, but let's go for the most important topic which we punted till today. Well, not punted. We scheduled uh we have the k-2.0 release candidate. Thank you so much tom for getting that release out the door. uh It's been used.

A

I've seen healthy conversation on slack as well as github, and even some on my email about some of the k2o stuff we wanted to checkpoint in the stand up about. Are we ready to push this thing as the default version? Potentially even later this month? uh I guess I'll pause there and let folks chime in on, if there's any blocking issues or pending issues or discussion, points that would help us make that decision.

B

Yeah, if I may add something, I guess that uh we have like received bunch of contributions since the rc was out, so there are a couple of new new prs merged in and I guess there is one one blocking issue which is which is related to the skilled jobs. It's like some memory memory problems, so sushi said he will look at it. So basically I think that uh once once this one yeah this is this is the one yeah. So once this one is, is merged uh or like fixed, we can.

B

We can probably release like uh rc2, probably something like that and just give it a few few days maybe a week, and then we are good to go with the with the final release. That's mine, that's my opinion.

A

Make sense yeah I saw the. I saw the chatter around the memory leak uh and I was surprised so I'm glad at least we narrowed it down to uh scale jobs being the the potential spot where the memory consumption is happening. So that's good yeah. It would be great to to fix this before. The final is out: okay, yeah.

A

I think that makes sense, given that like this, whatever change here might have some impact um and so kind of the proposal on the table which which I would uh agree with as well, but I'm open to conversation, which is we closed. This issue uh as well, as you know, we we did merge in a few pr's recently as soon as mentioned, so we kind of take the status of those in those net new prs. We do a quick rc2, which is kind of uh hey we want to. We want to double check.

A

To make sure nothing is is is off before we make this the default um and then from there like, potentially, if all that happens in the next week uh a week from now so on the 22nd, um we could have a similar conversation and see if rc2 went well enough and we want to go from there. Does that sound fair to everyone? Any questions concerns yoshi. I know you're on the call. Are you good with that plan.

H

Yeah absolutely yeah, I I I was sorry to have yeah yeah, create a pl for this.

I

uh Just curious, you should you already know what the problem is uh and yes, okay, good question.

H

Yeah this is uh yeah gcp scala with uh he. He he did a detailed report on the slack and uh yeah. It is uh probably memory leak, yeah right, so I'm gonna, I'm gonna, do the profiling and yeah reproduce it.

I

H

I

Currently actually know the fix, I'm just saying why I'm asking is that because look like we are, we are blocking on the release, uh and so I just I'm trying to get a sense of uh like do. We only know the problem. How long will it take so just just curious from that perspective,.

A

Right go for it seriously. Sorry.

H

Yeah yeah: we need to start with the investigation, but I believe that you know the memory profiler might help to identify the spot. Okay, fair enough.

I

G

There are also some people are having issues with scale down to zero. I think, but I'm checking if it's related to the the cooldown uh not being configured or just using scale it and doesn't support it, but I don't think that would be a blocker which we can easily fix after 2.0.

A

Yeah yeah tom and I got looped into some. It was another team at microsoft, actually that's using cada uh and they were uh it's funny. They they're in microsoft.

A

They found tom's email somehow and they just immediately emailed tom and they're, like hey we're, having issues with cada, and then tom was like, oh by the way, there's a few folks at microsoft who might be able to help you as well uh but yeah they were, they were saying they were having they weren't, seeing the cool down period being honored uh at the time, though they were at v1.

A

I think we asked them to try in v2rc and see if that fixed it I'll have to dig up the email and see where they went, but uh I'm not. I guess I don't mess with cool down period too often, maybe that's something I can quickly repro.

A

I have to build a cada demo for kubecon for the microsoft booth anyway, uh maybe I'll I'll play with that and just do some smoke test validation that I'm not seeing the same issue: um uh okay, that's great, yeah and and I'll I'll keep an eye I'll try to keep an eye on this issue. I wonder if I can notify for updates just on this one.

A

Just that sometimes memory leaks can be a real pain in the butt to define, uh and so, if this ends up being extensive, uh we'll have to uh we'll we'll do what we can. I guess.

A

um Okay, it looks like I'm already getting notifications for this issue, so uh anything else on k to 2.0 that folks want to cover okay uh roadmap review tom. I believe this is yours. I know I have an email that I don't think I've opened yet around this. Is there a repo here any do you just want to talk about it? uh What's the best way to talk about the roadmap stuff.

G

Yes, so there is now a project on the main ripple, which just shows the idea we had previous meeting. I just added a bunch of issues I think we should tackle.

G

The alternative approach is to create a dedicated roadmap repo so that we have a clear separation of the roadmap and planning, and then the technical implementation issues and the bugs to clearly separate them, um but I'm pretty flexible, uh so would be good to have feedback on that and then the next step would be to really add all the roadmap items. This side to which we want to commit and uh yeah take it from there.

A

Yeah, this looks great tom. I actually did. I did open this email because I actually know I have looked through this uh so yeah for folks who saw, as I shared my screen, if you go to the keto repo and projects, there is this road map here. um Where is this open for anyone to create proposals right now, or is this kind of restricted to owners, and we can pull specific issues that we feel like are big enough to warrant showing up on the roadmap.

G

Yeah, so they have to be manually added, because github doesn't support automatically, adding issues with this specific label so either we add all issues or non, so I prefer. I.

A

G

But I also introduced two new labels called the roadmap and the roadmap proposal. I think so the maintainers could use that and then do the manual action themselves. If we think it's a roadmap item or not.

A

Great great yep, that makes a lot of sense. This looks good and I know uh in one of the areas we're maybe going to talk about this week, but maybe we'll do uh in two weeks is uh some of the cloud advocates at microsoft have actually been building some pocs around first-class http, based scaling that I know they reviewed with honored and ahmed uh earlier this week um that they were gonna to bring up it uh to stand up and potentially open up a pull request there. So I think this is good.

A

I think this helps folks know you know what what is next, like, hey, cata 2.0. Does that mean we're done, and it's like? No we've got a bunch of other big things to do so. I think this is great now we're putting that together.

G

If we want to have the automatic adding to the project, that would be an argument for a separate repo, because then we can use.

C

G

Template surely for entirely for the roadmap but yeah we can see what people think.

A

Yeah I'm open to either. I think the way you've set it up now and kind of how you described where it's a little bit manual, but we have some filth or some tags at least to help us guide us in which ones we should add. I I think we could go with this for a bit and if we find out it's too cumber summer, we're leaving things behind, we could look at doing a separate roadmap one, but this looks like a great first stab at it. So thanks tom.

G

Okay, I have to drop now, um but I'll I'll check the notes afterwards.

A

Okay, we'll have a heated discussion without you, tom, enjoy the rest of your event.

A

Okay, see you later bye, uh okay, great uh any other comments or questions or thoughts on roadmap. Before we move on to the next item cool this one might be pretty short, I think it impacts the uh uh american folks the most. So I don't even know where all day life savings come into factor right now we are meeting at this time um which, for me, is nine o'clock a.m. uh Pacific daylight time come november. I believe it changes all the time I think.

A

On november 1st, all the clocks will move back an hour and so um right now would actually be eight o'clock in the morning. I know last time, daylight savings happened. We bumped the meeting out an hour so that it stayed at 9 00 a.m, but it would become an hour later for everybody whose clocks don't change. Is that right? Am I thinking about this correctly?

A

uh No, maybe it's the other way around. I'm sorry, I get confused. It is fall back. So right now would be eight o'clock yeah. I know it would be an hour later. I'm sorry I'm I'm confused, but I know we also move this time before, and so I think I just wanted to have a question here which is like what should we do with the stand-up time coming that daylight savings is coming shortly after our next stand-up?

A

Do we keep it where it's at and folks who have daylight savings need to adjust and join at 8? Am do we bump it an hour later, but then folks have to join an hour later any thoughts, and I'm also still hesitant that I actually have the math right here of what happens on daylight savings to everyone else, um just because I'm talking and thinking at the same time so I'll pause there any general thoughts or votes, especially, I guess um honorary I'd, be curious on your take of what works.

B

If I may jeff a little bit, uh I guess the main problem is that uh we like in europe or, for example, in chicago we have the they like. They like saving time, like probably like a week or two sooner than in the us. So this is.

A

The sure main point.

B

A

And is it the same, your your clocks will go back an hour. Yes.

B

It will be on the 25th of october.

I

So uh so, if that is the case, then probably we just adjust and it'll adjust for both of us right.

A

Yeah they're one week earlier because we're november first yeah.

I

But but we are also meeting once and two.

A

I

If you don't fall on that, then we may not even have a meeting or we can even skip a meeting if required. But uh but just my preferences to like eight o'clock is a little bit early. So for me uh personally uh so especially with you know, you know with all the coverage and yeah.

C

School, it's school schooling.

I

Yeah, that's the time when kids are getting ready for classes so uh yeah. So so, if it turns out that even europe has uh actually has daylight savings and they are falling in the same way, then then I I guess we can, I think it still. It looks like it. We can still coordinate right and keep.

B

It, yes, I I think that like personally for me, uh I don't I don't mind uh like starting uh one hour sooner, so it's okay for me to to stay on the same same time to be convenient for you.

A

Okay uh and sorry, I think it's actually 1700 utc is what we'd be proposing, um so we would shift with that. It actually makes you feel better yeah daylight savings is such a weird thing that I'm like I don't know how unique this is so they've been like. I feel good at least that your clocks are moving. I don't know all the other parts of the world that are on the call.

A

I don't know what vote you're in, uh but I think right now we're looking at saying, hey right now we're meeting at 1600 utc uh after november. First, we might actually move this to start being at 1700 utc so that more or less it's still the same time, if you had daylight savings, so it's still 9 a.m. For me, it's still whatever midnight for zivian, uh but we would shift it there.

A

uh But for folks who, who aren't being impacted by daylight savings, it would mean that this would now be an hour later in the day, concerns.

B

All right, I think if I made something to this topic, uh I discussed this with uh with tom before uh about moving the the stand up to another day in the week sure, because tom told me that he will be like probably like very busy next, like a couple of first days, maybe like for the rest of the rest of the year. So I was thinking about moving it to tuesday, because on first day there is the cncf.

B

Serverless is meeting the same time that we are meeting, and the other point is that, like uh we are discussing the releases so like. Usually we like agree on the release on first day and then we are doing the release on friday, so which is not very good. So if we, if we meet on tuesday, we can discuss on tuesday and then we can release on on wednesday or whatever. So this is just the proposal if it is convenient for you guys like meet the same time on tuesday.

I

Yeah, it doesn't matter to me personally, uh but uh I'm just curious, uh but friday would not be because then it'll be friday night for.

F

J

Then we'll be doing releases on saturday.

F

Yeah yeah yeah friday there's another option for me. Sorry: okay,.

A

I know yeah, I think tuesday works well for me. Actually, uh so why don't we do that? Then? uh I think that makes sense uh and yeah we. I I do miss 100 of these serverless sig uh cncf groups, because it conflicts with this meeting, which is fine. I like this meeting more uh no offense to doug on from ibm uh who I love dearly uh but yeah. Why don't we do that? Both then uh we can.

A

We can move to tuesdays and also adjust the time starting on november 3rd, so yeah, I think our next our next meeting, then I guess right now. We have one on the 29th at the same time. So maybe we keep that one, as is um which means sibianic. You can just join an hour earlier or later. I can't remember, I'm all confused again. um I think you get to join an hour earlier uh and then we'll start on like november 10th is when we'll switch to tuesdays.

B

Yeah, that's perfect.

A

A

Sweet all right now we get to talk about fun stuff now that we have kind of the the whatever out of the way, so uh richard jess, callum I'll turn it over to you, and you can talk to him about this ibm mq scalar. I saw that there's a pull request already, so maybe I'll open that up as well, but feel free to share your screen uh or talk to it. Whatever you want to share here,.

D

Thanks jeff, so just a little bit of um preamble for me, so uh we're from the ibm mq development organization um each year we welcome graduates into the organization and set them a project.

D

Ibm mq is a well-established messaging offering from from ibm we're on the mainframe, we're on the cloud we're on the raspberry pi, we're on many different architectures on distributed, containers openshift, you name it. We have a server offering there for this year's project. We thought it'd be kind of cool to get a cada scaler in place, so the team have been looking at over the last few weeks and I've got to a point where we put a pull request in.

D

So we're really really excited I'd like to hand over to the guys to share with you what we've been doing. I'd love to take some questions. If that's the right thing to do, I do have a couple of questions myself. Maybe we can handle those at the end if you'd like to find out more about us, if you go to ibm.biz forward, slash, learn dash mq, that's a dash uh jeff! I think we've got a slash in there instead.

D

So it's ibm.biz and then forward slash, learn, dash, mq, perfect. You can find out more about ibm mq there, where we run those kind of things just for some background, so I'm going to hand over to jess and callum just to talk about what we've been doing and uh they'll take it from here.

K

Oh yeah, can you guys hear me okay,.

C

K

Cool cool- that's always a good start, um so yeah as richard kind of said, so we're doing this. We had four grads actually this year, which is just a little bit smaller than normal, and we've also had two placement students joining with this, um and the idea was kind of to uh get to you guys and hopefully create a pull request and- and we think we're we're pretty much there as you can kind of see on the screen- I guess yeah.

K

um So what we've actually got is we've got pull requests for the actual scaler itself, as well as the docs, and I think we've already got merged in a link to our sample app um right. So we've done a go sample app as well, which is fully documented as well at the moment. Those docs, if you follow that it takes you through actually installing a local instance of uh cada and playing it. That way, because you've got to put put the scaler in, um but hopefully you know fingers crossed.

K

We can change all that soon and uh have it uh straight from from you guys through that call request. um So that's pretty much where we are. um I think jess is gonna, give you a bit more information on kind of? What's what's next for us and a little bit more on that kind of thing,.

C

Yeah cool so um we're in terms of those three things that callum just mentioned: we're um addressing a couple of comments that have been put on those pull requests and if anyone else does want to take a look and make any additional comments, that would be awesome, um but other than that we just have the um integration test aspect to have a look at.

C

um We were actually wondering if there would be anyone willing to give us a little bit of a helping hand just that we are completely new to the framework of the integration test. um So, if anyone's even willing to just take um any questions from us when it comes to us developing it we've kind of started, um I'm coming along with it. It's just um it's a bit slow progress. Just because we are new to the uh testing framework that you've got for the integration test.

A

Yeah anyone want to.

C

A

Here wait: we can actually stop yeah. I am curious, I know he's not on the call this week. He usually is. I think the last person- uh and I was even gonna check to see if the commit log backs me up. I think the last person who's been doing a lot of work here. Around test is travis.

A

um Who is super great in a bunch of ways? I know he's on the slack channel as well he's not on this call, but he would be one candidate who, I think might be be a good option to reach out to for questions um as well. Unless I'm misremembering, I know there were a few folks from uh who've been doing some test stuff. I don't know if anyone else on the call would be a good candidate as well to help answer questions on setting up some of those end-to-end nightly.

B

Yeah you can can fall back to me as well, like there's, no rope, no problem. I guess the travis is in the uk, so he's in the in the same time zone as you guys. Oh.

C

B

Yeah perfect, thank you um feel free to ask on slack, probably that was the best best way like on the other channel, so probably like.

C

B

C

Yep sounds good um yeah. I think that was the main thing that we've kind of got remaining to work on other than that is just the pull requests and addressing any comments, um and hopefully to get that in in time for v2 fingers crossed great. um Oh yeah,.

K

Yeah, I think we're in a pretty good place. So what we've done is we've uh when we made this scalar we've based it off of v2. To begin with, um I think that was kind of the direction we were. We were pushed towards, that's what it went for, um but yeah, I think I say I think we're in a good place.

K

So we've got uh all the uh normal unit tests and things that's all done in passing um and we've got, I say a demo that can be that people can go and run right now and we've got uh you guys might know about ibm cloud and our own infrastructure, so the entire demo can actually be run on our infrastructure on the free plan. So it's it's not like we're limiting this to the clients who are going to pay the most kind of thing.

K

D

Jeff, just uh just a couple of things to wrap up, I I guess, from our perspective, um be great to get a little bit help with that integration test. um I know that's relatively new and we'd like to get that over the line, so yeah we'll reach out on the slack channel um to do that. So thank you. um The pull request. I think we've got in a little bit of a tis because uh things have been in and out and uh zibanek.

D

I know we spoke earlier and I think you're willing to try and help us out. We've been sort of tidying all that up. um Please don't put it on the screen. It's horrible!

D

It looks right, yeah I'll switch to the code now we'll I'll code review. It live! Oh great! Thank you. That's awesome. um The other thing that I had a question about and- and we may want to follow this up offline- um is that there's a little bit of confusion from me around the contribution terms. So I followed the contributing tab and I've got approval to submit the pull request under those terms.

D

There was then just a comment on the pull request: asking us to remove copyright and to remove the apache 2 assertion that just came up as slightly unusual looking at this as a contribution, and I'm not clear as to whether this needs to be a contribution or a code donation. So I don't anticipate any problem from my end in in fulfilling either of those. It's just that I need to be clear with the uh the guys here, the team here, I'm working with on the legal side to make sure we do the right process.

D

If that makes sense,.

A

I see, or I think I see I assume zibianik you were the one who was looking at it.

B

Yeah yeah, yes, like there was the arpeggio license with the with the ibm like the copyright, so I wasn't sure that this is like acceptable by cncf like to have sure, because we have like the project copyright on the on on license in the in the repo. So uh so, where? Where does it pop up like? Where did it it is it is? It is already removed. I suppose, like in the um that.

D

That is a kind of transient state for us at the moment. So for a contribution um we would be typically looking to to include the copyright just because that's the statement of fact and we would make the contribution under apache 2 and that that's perfectly fine. I wondered if this was a house style question. um So if it's a house style question, then we would offer up the pull request.

D

We have there with a comment saying that we've removed the comments in each source file for compatibility with the house style, um but I would need to add to the comment that the the copyright assertion is unchanged. um If this isn't a contribution, it needs to be a donation, and I need to work through a different process, and I I would like a little bit of clarity in the contributing tab, because that very much is going down the contributing um um sort of process.

D

um Certainly from my perspective, I don't think this is a big deal. It's just clarity right and um I don't want that to detract from how excited we are to have a scalar and to get ibm, mq, clients up and running with this stuff.

A

Yeah, no, it makes sense. It's a it's a fine topic in canada. I think xavier x, probably coming for the. You might actually know a lot more of this than I do. I I think my my initial assumption is, like we've got a few contexts on the cncf org, more or less we're kind of just like hey, you know, walked itself whatever it's mit licensed and it's a part of the cncf.

A

Oh no, it's apache licensed uh in cncf yeah. It was apache license when we went to the cncf. I don't know a whole lot about this licensed stuff or what's there, your request makes sense. Like I understand, copyrights are a thing, um and so I think it's more of I'll, probably loop in, uh like our main contact from the cncf and be like hey what are other projects doing? What's the recommendation?

A

I'm fine either way, we'll probably just do whatever the cncf guidelines to have us do and then to your point. Whatever the answer answer ends up being make sure that it's clear in the contributing section. um So uh I'll do that and then maybe I don't know uh who's the best point of contact. But if there's some email, maybe you can stick an email in the chat window.

A

I can include you on those emails so that if you have any questions uh you can ask the cncf reps directly, since I I'm I'm very ignorant around all things licenses and open source.

D

Sure, thanks jeff I'll, certainly um ping, your own email address and um we'll take it from there.

A

Great great, this looks really good. The only question I have two around this and this might be minor, but since ahmed's on the call I know we made the change in v2 that if something is being loaded from an environment variable, we appended it with ref, given that they have username and password here that are in that world. Does this need to be username, ref and password ref? Is that what we landed on.

J

uh Well, will I let from n uh as a suffix, oh from m- that's what it was yeah, but I think yeah. I meant to comment on that for requests. Currently they don't read um username and password from enviro. um It might be a nice thing to support, but we only read it from the auth parameters.

J

I see uh okay yeah, so I think it's fine now, because off-branders don't have the from and suffix, but if they want to support having the front end, then you need to add it from the metadata. I.

A

Can follow up on the program I see uh I see I didn't even realize there was a way you could do exclusively from off parameters and not also do it from amph, um okay uh yeah. So I guess it is kind of up to you in in some ways. I don't know uh folks on the call, if you, if you got the gist of the conversation back and forth there, uh did that make sense to you at all of the decision to be made.

J

uh Yeah, that meant so go ahead.

C

I was just saying yep that sounds, makes sense, um I'll see what you mean about the from end. um We just went down the orth params group, um yeah.

A

Yeah, which is fine like honestly, I can see a world where it's like look we, for whatever reason we just don't, want anyone to do from amp. Usually we do that like historically, I guess we've done from envelope for like ease of use in terms of you only dealing with one thing and you're dealing with environment variables.

A

However, you want, but especially when it's something like a secret, more often than not people or I guess from em- can be from a secret as well directly in line it just means they don't have to deal with this extra crd, which, whatever this is ten lines. So uh I don't know if we have a official stance where it's like we require from anven and for off parameters. I cannot blame fine.

A

If people do this route as long as it's clearly documented that it's like you cannot do from m, you have to do trigger authentication, uh since I think the default for all of the other scalers is that if it's something that could be in trigger authentication, it could also be an inline secret or an inline environment variable, uh and it would also resolve.

A

I don't know folks on the call have more strong opinions on. We need to make sure that they're always from enviable.

J

I mean all other scalars have that, like all other scalars that have secrets support from and from the metadata directly, um I'm not like, ideologically opposed to having a scalar that doesn't. But it's up to you guys.

A

Sure so I guess maybe put otherwise uh if, if you're not opposed to having from m, it might just make it. So this isn't the odd odd duck out uh if we changed it, if we just add that into the code so that it could also be from m, which would also mean to be consistent with v2, the parameter names would change to username from m and password from m, as you can see how we've done with a bunch of these other ones uh in the change log. Just so that folks know.

D

Jess is that something we can take care of in the.

C

Pull request, and we can definitely just add that in it doesn't make too much difference to us right so does it effect? Does it affect the sample at all?

C

uh No, it shouldn't, do you know an additional option right before to supply it, but it shouldn't affect any of that.

D

Perfect, okay is that does that work for you jeff? Can we just take care of that yeah.

A

This looks and honestly this looks fantastic, so I'm I'm thrilled to uh I. I assume the sample, uh and this is again my ignorance, like I know, of ibm q, because I've had a good few azure customers who use ibm mq. I personally have never spoken.

F

To here, jeff great yeah.

A

Yes, uh but like I'm even keen to to test this out or add it to my my demo suite so this looks great.

D

We've got a little learning journey there, so you can get yourself in the claim badge um and there's a little um hand on code, hands-on, coding challenge and a little quiz at the end. So you know if you want to go see that you'd be more than welcome, um but I'm happy to do a call if you, if you want to talk about a little bit more about what we're doing in mq land, um just a couple of things so we'll take care of those changes. I think we just need to tidy up the license.

D

Clarity, I think that's all. It is um jeff and the wider team just really important to note that um jess and callum have only been with us for a few weeks. They didn't know a great deal about mq when they they joined.

D

They certainly didn't know anything about cada they've, grabbed all that technology they've used your dock and they've delivered a scale, a scalar within that team of four, which I think was really quite amazing, and there might be some benefit to just them, telling you their story and how they went through that on another time. There might be some changes that you might want to consider as a result of that, and there might be some.

D

You know some great feedback and discussions that will come out of it and on that point, um just wanted to check with you guys that it would be okay. If we put someone on the call um every every couple of weeks here just to um keep in touch with what you're doing and that kind of thing, I guess specifically wondered if there was any uh sort of approval for that or whether you know you guys be happy just to see us come along.

A

Yeah we would love to have you come along and honestly it's it's fantastic, I'm I'm I'm flattered and thrilled that you chose keda and an ibm, mq scaler as the thing to ramp up and learn uh and yeah. Absolutely, I would love. I know we're we're running a little bit short on time this week, but whether we do it in a future stand up or even on slack, is we've kind of mentioned. All of us are active and listening to slack like understanding what that was like on boarding and ramping up and using it.

A

We dug into it a few months ago. I think in terms of trying to clean up the contribution stuff. Maybe you benefited from all of that and a lot of the the the pointy edges were cleaner. I would imagine, there's a new set of pointy edges or maybe slightly dulled, edges uh and yeah. All of that is fantastic. I'd love to learn more.

D

Yeah, that's great, we'll we'll um make difference come along and participate for sure um we would love to do that and if some conversations spin out of it, you know we'll take part for sure.

A

The other one too that's an option depending on your level of interest like we do have on the cada site. This blog, um that's pretty sparse, like we use it from time to time. If you're keen to do just a blog as well, to either explain about your experience in contributing or anything around cada, that's something I know we'd be thrilled to help promote from our side on whatever channels we can as well great we'll we'll take that back to the team. Thank you. Sweet thanks. Al thanks for joining great meeting you, okay. uh She.

D

Can do the merch now jeff.

A

Yeah I mean without tom I guess he just wants us to vote, so we can vote for tom's sake. It looks like we have two options for merch uh and let me make sure I'm reading these. What do you think of current designs? Can we have a mix of one and two?

A

uh Can we fill the lightning bolt with white to make it more clear, yeah the favorite feature, which is the do we know who designed these was this tom who designed them.

B

No, I guess it's it's um some provider from from cncf, oh.

A

Wow so one of the perks of being in cncf is we get swag designed yeah, but I miss.

B

I'm missing the lightning bolt over there, so that's something.

A

B

Yeah so so the feedback.

A

Is fill in the little lightning bolt here so that it's white option one or option two. Anyone want to vote via chat or by unmuting on which option they prefer the most.

A

I like option one, I know tom, said a combination. I wonder if he means like option two in the front option, one in the back, but I I I'm a fan of just the logo straight above the heart iron man style, uh uh but yeah. I I think the the option, one with the filled in lightning bolt, so that it's a little bit more clear. That's my vote.

B

A

B

I I think I think the same. I think the same. I guess that uh tom was proposing, or maybe it was my original. My proposal like to have like one color or like with the different designs, so like probably the mint one with the with the small logo on the other side.

B

So we have like a combination of both.

A

Meaning so like the same shirt or we just get both shirts ordered.

B

No, I mean I mean, like the gray and uh blue from the option, one and the mint from the options.

A

Oh okay, yeah uh I'll! Let you in tom figure I'm okay with this.

B

Sorry, for the come sorry for that.

A

It's on the agenda uh yeah- I I honestly am just I I didn't even realize we had it's funny. I ordered a bunch of kedah shirts right before the pandemic, to give out it at, I think, kubecon at the microsoft booth, uh but then kubecon got cancelled and now they're sitting in a closet and a storage closet back at microsoft headquarters, um but they they weren't nearly as cool as I actually think I just did this design uh the navy option, one more or less. I don't.

A

I couldn't tell you what the lightning bolt looked like, though uh okay, so we should get a lot more cada shirts out in the wild um I'll give this update from tom worth noting so there's a a uh a series that happens on the azure developer channel called azure fridays that they just do like a 10-minute recording of like hey, here's, a little bit of tech, and then it gets viewed by some whatever thousands of people.

A

uh Tom's gonna go on the show and talk about cada uh and, as part of it, he's going to show his service bus sample. So he moved that to 2.0 um he updated the pot identity so that he can showcase k2o along with his sample um at this azure friday kind of marketing spiel. That will probably be published a little bit later this year. I think he records in early november. um So that's great.

B

Jeff jeff, if I may uh relevant to this, probably we will need to migrate like the rest of the samples to v2.

C

B

Check if they are needed to be to be to be migrated.

A

That's a very good point: um yeah, that's a really good! Maybe.

B

We can you can, we can. Maybe we cannot issue and so like it is good for newcomers. I suppose.

A

Yeah, at the very least, we need to clearly mark like, if we're not going to manually, upgrade the samples like flag, which ones are v1 and which ones are v2, maybe put v2 below a fold or something um but yeah you're right, there's a lot of samples here and a lot that will need to be updated.

A

um Yeah, I'm! I was because a lot of these linked to other repos, and so maybe I'm trying to think if I have a meeting later today where I can just open a lot of these and create an issue. That's like move to v2 and then see what happens with it and if it doesn't, then we just have to make sure that folks know this is only works on v1 um and we'll probably put like a line here. So I'm glad you brought that up. That's a that's a good issue!

A

um Let me move samples to v2, I'm going to create the placeholder issue here. My github notifications are consistently underwater. So I'm going to add a item for me in my own personal to-do list that does not have all the things to track this and I'll. Take some action here, uh jeff to ping the sample to move okay uh and then the last one we have is helm2.

A

I think travis was the last one who's going to look at this and he's not on the call today- uh and I guess his proposal is just: do we deprecate helm2 for cada 2.0.

B

I guess that tom was a little bit frustrated with the with the help too. So we were thinking about about dropping, dropping the support and just just like moving to v3. I guess it's. Okay,.

A

Yeah and it looks like helm2 itself- is reaching end of life, so it makes sense um yeah. This tweet is pretty convincing. I I honestly am not as bothered by the the crd errors, but I know folks have run into it and tom despises it uh so yeah. I I think that makes sense. I'm okay with it.

A

Okay I'll, create an issue on the charts repo. uh I assume yeah they're, like people who are using older charts like they use a specific version. If they were using too it's not like that's going to break it would just be if they try to use the latest charts. It would only work with home too. Is that accurate? As far as you know, xavier? Yes, I suppose yes yeah, and I know there's already an issue here as well on um this one. So I'll just add here.

A

uh Okay I'll, add that issue all right. That's how we have on the agenda, then, I think we're cool too. We are okay to remove helm 2 for the cada 2.0 charts, given it's going end of life in november.

A

uh That's how we had on the scheduled agenda. Any other topics folks want to bring up or updates they want to share before we sign off.

D

Did you want the uh team ibm t-shirt, sizes jeff, so we can get a t-shirt or.

A

uh Yes, we're not shipping them out, but that's the other question once we get these t-shirts, how are they actually getting distributed until we start having actual conferences uh in person uh tom's, not on the call to answer that question?

A

Maybe the cncf also has a shipping service and we can start taking. uh I I would love to do that honestly. If, whenever you contributed, we got your address and we sent you a shirt. I'd be totally on board. Definitely.

D

You should start should start now.

A

Hey at the very least you could we are participating in oktoberfest. If you just add a hacktoberfest flag to your pr and get it uh approved, you can get a shirt from digitalocean. I guess, though, it.

D

Says oktoberfest.

A

D

This is the insights. I need thanks. Jeff yeah, I'm gonna stop talking now I'll. Let you take some serious aob right.

A

Yeah no worries these are the topics we need to take time for so I appreciate it all right, thanks all for joining I'll, go ahead and upload this to youtube and we'll talk again, two weeks from now same time, except for zibianek and folks who have earlier daylight savings, you get a little bit earlier. So talk to you then.

H

See you thanks.

A

H