Add a meeting Rate this page

A

Okay, queue builder controller, runtime and control our tools meeting for April, 23rd 2020. As a reminder, this meeting is being recorded and will be later uploaded to YouTube, so do not say anything that you do not wish recorded for all posterity until the end of time, or at least the internet Hey so looks like we have three things on the agenda today. I think Joe has all of them so Joe. Why don't you take it away? Sure.

B

So first question I brought this up last week in the communities flags. In the queue builder channel, we merged the community's 118 version bump into control a runtime like a month ago. We've got a host of other updates on master, some of them breaking some of them. None I was wondering.

B

Should we go ahead and kind of release for either 0.59 X or B 0.60 so that we can start getting users using the controller runtime with 118 seemed like there were some consistent consensus in the flash channel, so I just wanted to get that across the finish line.

A

Yeah that seems reasonable to me.

A

Yep sounds good I'm curious if folks are interested in doing a 0.5, X and getting stuff back ported or if most folks are just good with going straight to 0.6, since we do have some stuff and it's breaking I am assuming by default, we'll probably go straight to be 0.6. So if you have concerns or comments as usual, or feel very strongly that we need another C release on 0.5, please do speak up.

B

Yeah my opinion I think you're gotta fix is perfect, I, don't see any reason to backward anything.

A

All.

B

Right next up so I can let Eric take this if he wants to talk about it more, but I just wanted to make sure we talked about it. He's got a PR up to emerge, the plug in phase one implementation into master, currently kind of on the feature. Branch. I don't know. Eric. Are you here yeah.

C

Basically, what I did was I took all of the commits made to the future branch in main repo and rebase the montauk ambassador and push those in to a new branch made of a PR against mastered with those rebased commits I just wanted to preserve all the history of the feature branch so that people can refer to it while they're. Looking in reviewing the rebase branch, you guys bastard.

A

Awesome yeah that's been on my I started. Reviewing it a little bit, I'm just taking glanced over and making sure I didn't see anything obvious, I kind of want, I wanted to finish doing the glance before I said anything and there's a lot of files. It's big, PR, yeah I think we're probably good at mostly just a glance because we've been intermediate reviewing but yeah so I, hopefully I'll have that finished like today or tomorrow, depending on.

C

Meetings insight ends, I will diligently work on follow-ups to that PR I think we can mostly, unless there's anything, glaring that prevents us from actually using plugins getting all of those convincing, as is and then doing a bunch of follows.

B

Cool yeah and I've got a I've got another review in progress on that to Eric so hopefully, today or tomorrow, I'm about 3/4 the way through I think.

C

Perfect I'm so.

B

So if anyone else is interested in this has has been participating in the plugin conversation or once know more definitely reach out to Eric and give a review of that. That's gonna be like a pretty significant change to how the queue builder CLI works, so we're definitely interested in getting some feedback. Ideally at this point, it's pretty late in the in the game, but if there's anything wearing that, you see. Definitely let us know. Okay,.

B

And then my last discussion point was so Camilla asked me earlier this week like so we've got this pretty big kind of breaking change. Coming in on cue builder, with the plugins PR.

B

Do we want to make a release of cue builder prior to merging that, so that we can then merge the plugins PR and then have some soak time on master before we actually cut another release that has the plugins implementation.

A

That's probably a good idea ideal. Ideally, the plugins is non-breaking right, true yeah, so, theoretically, in in an ideal world we could release with plugins and and no one would notice anything practically I, yeah I, think doing a release. First is a good idea, just just in case like something is terribly wrong. We have something for people to refer back to that's still reasonably new.

B

So I don't know when we think we're gonna. It seems like the plugins PR might merge- probably not like they're tomorrow, but maybe sometime next week.

B

So we want to try to plan like when we'll do the pre merge queue builder release, or do we just want to do that? One by ear.

A

I.

A

Think we can probably just do that by ear and we might just be able to cut it like just before the thing merges: okay and so I'm imagining. What we'll do is we'll just like we'll put a hold on it once we get. The final looks good to me and then we'll do the release and then we'll on hold.

A

Yeah.

A

All right does anyone else have anything that they would like to talk about.

A

Buddy back 45 minutes, so I hope you all enjoy your day and I'll see you in a couple weeks. Everyone.
youtube image
From YouTube: Kubernetes KubeBuilder Meeting 20200423

Description

KubeBuilder Meeting for 2020/04/23. See https://sigs.k8s.io/kubebuilder for more details.