VMware Carvel Community Meetings, 26 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Carvel Community Meeting - August 26, 2021

Description

Carvel Community Meeting - August 26, 2021
We meet every Thursday at 10:30am Pacific Time. We'd love for you to join us live!

Team covers project roadmap and new release of kapp v0.38.0. Full details here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#August-26-2021-Agenda

A

There we go all right, hi everyone! Welcome to this week's edition of carmel community meeting today's date is thursday august 26 2021, uh just a reminder that these are being recorded and uploaded to youtube, and we ask that you please read and abide by our code of conduct while attending these meetings uh for those that are watching from home. We encourage you to come and join us live it's an opportunity for you to come, listen in on what the maintainers are working on and bring anything you need help with up with the maintainers themselves.

A

If you aren't able to attend live, we also encourage you to join us on our slack channel. Then the kubernetes select workspace at carville and on twitter at carville underscore dev.

A

When you attend these meetings, we ask that you put in your name in any organization that you're representing and in addition, um if you're using the cargo tools, we want to hear more about how you use any of the tools. You can add those specific comments to the pinned issue. That's on the car main cargo repo- and you can add your organization website, contact information.

A

Specifics about your usage of the tools and upload the logo of the organization that you represent, so we can help promote your organization.

A

On to announcements, it's a reminder: we do have a workshop at spring one and it's next week, thursday september 2nd at 1 30 pm central time there are seats still available. So if you are looking to get more familiar with the karbal tool suite, this is a great opportunity for you to get hands-on with the tools.

A

It's a 90-minute workshop, uh we'll have maintainers online to help. You hope we work through any of the the um the options in the workshop. So we really encourage you to sign up and join us for that.

A

Additionally, we do have a talk. You can also attend if you're unable to attend the workshop.

A

And then next up we have a release for cap 0.38.

A

And does anyone want to go over the details behind this release.

B

I could do that so this was.

B

A few issues that everybody in the team has worked on a couple of major ones: one is having the ytt base, rebase route introduced, and second one, I think, is the keeping the version to keep original annotation that we have added here.

B

Others are pretty straightforward uh documentation, for these will be coming up soon. uh Anyone has questions or do you want me to go over these.

A

High levels, that's great, if there's anything else you wanted to share, in particular, for this release.

B

So the version keep original adds onto the versioned flag, a version annotation that we have. That means, if you want to keep the original uh record along with having a versioned resource created, it will help you do that. So that is one part um there is um the vitt-based rule.

B

I think uh rebase rule is something which has been introduced to uh help cases where sometimes secrets get uh added quite often right, and we don't want to keep updating apps all the time for that, so you could have rebase rules added, which would let you not change.

B

Apps update apps during those times, so a lot of use cases interesting use cases for that I will defer to the documentation, is completely done to speak on that more in detail.

B

It was, uh it was our, I think, as a team, it was our first uh um release after this immediately we have done another release. That is three nine: to uh solve an issue which is showing warnings a lot of warnings in in the latest kubernetes version, so that helps resolve that part yep.

A

Great. Thank you for that.

A

Okay and uh before we move on to status, updates, just a reminder, if you have anything you wish to discuss in this meeting, please add that to the discussion topic section below the status updates and we'll get to it,.

A

Okay, next up, we have project roadmap.

A

Are we looking for the private registry authentication for cap controller.

C

uh Joe, you want to share.

D

Yeah, I mean pretty good right. I think we're in the final stages of cutting a release uh today tomorrow. uh uh So I think, that's that's all coming together nicely.

C

And- and I guess like the only other thing I would share for now- is uh we do plan to give like a a lightweight demo here once once everything is released so so get excited.

A

Awesome thanks, erin, okay, the other items, any updates, in particular for those for the two that are coming up in september.

E

I can't give a small update on the export ytt schema as open api schema. um We've been working through the proposal on that and um things are starting to come together. uh The proposal is available in the carvel repository you're. Welcome to review that provide any feedback.

E

um The feedback, like the initial feedback deadline, was today so um as long as we can reach a kind of convergence on next steps, there we'll probably begin the work pretty soon.

A

Awesome thanks carrie.

C

And maybe just a more general note regarding the road map, um there's there's a whole bunch of things that are in like the tbd timeline state. um Recently, we've we've been doing some kind of like road mapping discussions uh most specifically for ytt and image package, so wanted to just like at least represent some of the things that are top of mind for us, but we're still actively working through. You know, what's going to get prioritized next um and how backlog will shape out.

C

So if uh there are any things that you know, you in particular want us to consider. Then now is a great time to service those.

B

um Yeah yeah even same for uh cap, we are trying to work on a few issues prioritizing them. We have to pick them from the unprioritized backlog into the privatized backlog. uh Interestingly, what we are working on is an issue to have uh externally created resources to be, you know visible when we are doing a cab deploy, we are still in the poc proposal stage. um Still some work needs to be done. Hopefully that should be something that we can see in the september release keeping fingers crossed we'll see.

B

Besides that, we have few other uh generic changes that we are working on and uh general note to. Let us know what are the priorities, um what what is it that we should be working towards? uh It would be helpful for us to prioritize our things.

A

All right, thank you anything further on the roadmap before we move on.

A

Okay uh on to carmel backlog, this might have been pasted from for, unless someone has any thing they wanted to discuss on this, or was it just an accident? Whoever pasted this.

F

It's still in progress, so it is valid. Okay,.

A

F

Yeah we're still working on it had some people sick myself last week, so that is in progress. There's a draft pr to capture these image-made metadata into the image package log file when emitting it from k, build and that pr should go into review mode soon and hopefully we'll get that out in the next cable release.

A

Okay, great, thank you anything um else from the backlog. That's not directly tied to the roadmap that the team is working on.

A

I see this particular one transfer, chocolatey repose to carvel.

C

uh Yeah, there's there's a number of things that are in progress this. I think this one in particular, is an ongoing initiative.

C

um I don't know if carrie or dennis have more accurate information, but we are working with, I think, adrian's from the community and just uh transferring the ownership of these chocolatey repos.

G

That captures it, and specifically right now, we're currently waiting to create a special repo to house all the scripts to make this possible. There's a there's a ticket pending for someone to create that repo for us.

D

So do you think that would be going faster if we specified that it was 85 or higher chocolaty.

G

A

Dark chocolate, jokes.

A

um All right, thank you for that um and shout out to adrian salas, who has been the main driver of the chocolatey repost for carpel, really appreciate all the work you've been doing there all right.

A

Anything else regarding the carpal backlog, what the team is working on this week.

A

Nope, uh okay and looks like we don't have any discussion topics. Is there anything that anyone has thought of that they wish to discuss with the team.

D

I could I could uh opportunistically, uh I wonder if we could just take a a temperature of um this kind of godok adoption, and I know there's uh in particular because we have the cap team here today. So in a few of the repos, we've been working on getting uh uh kind of go dock. uh There's like a linter setting where you can just be like from this point forward. Godox are now required for uh exported names.

D

Basically, so it forces us to ratchet in our documentation- and I was wondering like uh john or the ytt team. I think you all adopted that a week or two ago is that, like too new to say, good bad.

H

Yeah, I I haven't uh done. I haven't had any um new code since that in ytt, so others would have to answer for that on the ytt front. If there's anything been anything like that, I think we've been doing a lot of focus on the proposal. Work.

D

Cool, so I guess I'll I'll just say: I think that it's been helpful in secret, gen controller and I've been trying to add in cap controller, uh and so I'm I'm kind of um happy to help folks working in other repos. The I think we have at this point like a a recipe or a template for how to bring that into uh each project uh and anyways. Maybe so, maybe there's a little more visibility since we do have an extra team today, but that's at the end.

G

I think it'll be nice to put an image package. I think, because there is an issue to kind of consume image package, not just as a cli binary but as a go library. It might be useful in that context, as well so yeah working with you or to get that set up, I think, could be beneficial.

B

Cool, we will also get in touch and uh we'll work on that.

D

Cool cool thanks all.

H

Yeah, joe on on that front, there there's a little bit of rotation from some folks from tools to tool like I'm spending a little bit more focus on image package soon and as a part of that effort, we specifically are calling out hey where there's opportunities to specifically go in and improve godox for exported elements.

H

um Probably new eyes are, are a great source for that kind of thing as well. uh It helps folks um ramp up faster on the code. If you have to explain what a thing is so that so, it is helping in in that way as well.

A

Great thanks for that joe um anything else from the team.

A

Nope, okay, all right! Well, thank you! Everyone for joining us this week for the carnival community meeting again, if you're watching this from home, we would love to have you join us live you can just sit in, listen in or if you have anything that you want to bring to the team that you need help with or you're wanting to provide feedback directly. Anything that you wish to share were all ears and we'd love to have. You join us and learn more about you and with that we'll see you next week. Thank you.

A