VMware Carvel Community Meetings, 18 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Carvel Community Meeting - November 18, 2021

Description

Carvel Community Meeting - November 18, 2021
We are moving to every 1st and 3rd Thursday, 10:30am PT, until early 2022. We'd love for you to join us live!

Full details on this week's meeting found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw#November-18-2021-Agenda

A

Hey everyone welcome to this week's edition of the carville community meeting if you're watching this from home as a recording, we encourage you to come. Join us live um according to this agenda. It says we meet every thursday at 10 30 a.m, but from now, until maybe january february, of 2022 we're going to be meeting um every first and third thursday of the month. That's just um as things slow down we're just giving some people some time, acknowledging that not everybody can be here, etc, etc.

A

So just giving a little bit more time in between meetings and so we'll still meet at the same time, but every first and third thursday. At this point and then we'll let you know whenever that changes.

A

um If you want to join us live, we encourage you to come, bring a discussion topic. If you have anything you wish to discuss with the team anything you need help with. You can put that down at the bottom of the agenda here.

A

If you want to come and listen in and just meet the maintainers you're welcome to do that as well. You don't necessarily have to have a discussion topic. um You can provide feedback as well on anything that the team is working on um just we would like to get to know you and and meet folks from from outside of the maintainers and learn more about you.

A

So we encourage you to come and join us if you aren't able to ever make it to a meeting and you still want to engage with us or anybody else in the community. You can find us in the carville channel in the kubernetes slack workspace. If you aren't a member of that workspace, you can simply request an invitation to gain access.

A

You can find us also on twitter at carville, underscore dev and at any point you're interacting with any of us or anybody in the community. Please read and abide by our code of conduct.

A

Next up, if you are using any of the carville tools, we'd love to know more about how you are using them. We have a pinned issue here and we just ask that you put a comment in here naming any organization you work for website all the details regarding that and the use case that you have with any of the carvel tools.

A

We utilize this information to help us understand how people are are using karvel help us, maybe improve the product itself, just get to know really how others are using it, and if you would like, you can put your logo within this comment, and we can add it to the adopters page for some uh promotion of your organization.

A

When you attend the meetings, we ask that you put your name here and the attendees section. It just helps us keep track of those that are attending these meetings and keep those lines of communication open.

A

Next step announcements so, like I said at the beginning, community meeting is going to move to every first and third thursday until early 2022.. We will keep you updated on on that. um We are also going to send out a survey regarding this community meeting so that we can understand what you want to hear more of or see more of what you want us to stop doing anything like that.

A

So please, when that survey comes out, we'd love to for you to fill it out, and hopefully we can get uh improvements made on the community meeting for 2022.

A

We have a couple of releases here. We have secret gen controller uh anybody able to go over this release.

B

uh I can talk about that one real quick. So um actually I lied. I made the change and I don't remember what we did. uh Oh yeah, okay, so it used to be that if you had a so this is all about star exports, which means secret gen, exporting a secret to all name spaces. Thanks nancy.

B

So it used to be that uh once there's a star export that every placeholder secret in the cluster would get that those credentials copied into it and somebody said hey what, if like. Basically that means that somebody can, even if they have a very little permissions, they can just have one name space that they have access to and they can just make a placeholder secret in that namespace and they're going to get every star export uh every wildcard export on the whole cluster.

B

That feels like a security hole, and so you know we're basically like yo. I hear you swiss cheese model, let's like put another layer to block that particular hole. So if you have a user who cannot edit the annotations on their own namespace, uh then you can put an annotation, I mean even if they can't but anyways the point is you can put an annotation on the namespace that blocks that any secret in that name space from receiving those wild card star exports.

B

So as long as your user can't remove that annotation, because if they can then like they've, just aligned the holes- and this was cheese once more- but as long as they can't then you've you've blocked that secret exfiltration and so we've we've made it one tiny, increment, um more secure. That's the secret gen 07x series 070 had a small bug in secret imports, which daniel helton very kindly fixed. So we we in good conscious. We can only recommend 071.

A

Awesome thanks joe, and I really could go for some swiss cheese now.

A

uh Okay image package: oh that two three.

C

Hello, so um on this new release, we fixed two bugs that were that that were found and made some bumps on on some dependencies.

C

um Basically, the the bugs that we were talking here about is, when you copy a tar file, uh a bundle that comes in the entire file into the registry.

C

We were not creating an images, location, uh translation information so that that was causing some problems, and this was fixed, and the other issue was that when image package always tries to mount images from one repository to another in the same registry, the problem is that maybe there are, you need different credentials for both registries and what was happening was that when you were trying to to copy to mount it, you provide the destination credentials and the destination credentials sometimes do not have access to read the other repositories.

C

So basically, this was causing some errors when you were trying to copy images from one repository in the one registry to a different repository in the same registry.

C

So what we did now is we make sure that the the the credentials used to write on the registry uh right but on the destination can also read the origin and if they can't, we don't even try to mount it. So we added like a like extra layer to make sure that those uh didn't happen. We also had some typos and nikolas similar did help us out on our template. So thank you for that.

A

Awesome thanks joelle and thanks nick appreciate the help. Okay. Next up, we have ytt 0.38 coming later today. Carrie you want to give us a little bit of what to expect there.

D

Yeah, so this is going to be the release where um exporting a ytt data value schema as an open api document will be supported. So if you have a data values file, you can make some quick changes to turn it into a data value schema file check out the docs in the website. There's a handy guide for that, and then you can just use that database schema file to export it as an open api document which can be used for documentation purposes. It can be used in a cap controller package.

D

There's a value schema section there that accepts an open api, v3 document.

D

So that's the main thing there's also some awesome. There's a bug fix for the way that data value schema works with any type.

D

um There's a bug fix for the way that we parse percentage size, and then we also got a community competition from uh rashad k um to fix some documentation. So lots of exciting changes in this release keep an eye out, should be here soon.

D

One last thing: there's also error message: improvements for data value schema, so you'll get some suggestions on. uh If you use a key, that's really similar to the key that uh was meant to be used. You'll get a suggestion asking. Oh, did you mean this key, so some helpful improvements there too.

A

That's super exciting carrie uh congrats on all of that. uh So once that is cut, I will send it all out to the interwebs and let everybody know when it's ready.

A

Okay, next up project road map, stuff.

A

Anything to go over here any changes, uh since I guess two weeks ago, since we cancelled last week's meeting.

E

um I I think this roadmap has collected a little bit of dust and hasn't been updated in a little bit. So no no real big changes to communicate here other than I think the releases that folks just mentioned. Some of these things are getting crossed off. um Maybe one other thing to mention: that's that's not captured on here yet is some of the carvel india folks have been working on a cap, controller cli and a first release of that which would really be a cli of feature.

E

Parity of what cap controller already does um would be, I think, potentially released either this week or next week, so so fairly soon um and yeah, we'll we'll get this roadmap updated. If folks would like to have any uh discussions or influence over the roadmap, you know we'd always be happy to chat about that.

A

Awesome, thank you aaron. um So it sounds like the this needs to be updated a bit. um Is there an action item there that someone wants to take on to clean it up.

E

If I take an extra item, while I'm muted, does it still count.

A

Okay, awesome thanks aaron, um okay, carmel backlog. Is there anything that folks are working on that isn't mentioned in the project roadmap that should be shared with the community as I need to know any interesting.

F

uh So there is one update I can give. We are also working on a few stories that are especially focusing on error message. Improvements uh like we are adding better display names in place of technical terms, and there are some documentation updates. We are doing for better use of ytt. Also few bug fixes that are already been one. One of them is already been taken, care that would be released soon, uh which is handling percentage sign for fmt and also we are. uh We would be adding more examples on ytt playground and also in documentation.

F

So these are some things uh in flight.

G

Yeah building off of that uh there's some additional error message: improvements in flight right now in uh ytc issue, 521 of when there's a syntax error in a schema annotation, hopefully displaying that actual annotation in line with the node that annotates, so that you can see the syntax error.

A

Very cool, thank you, varsha and garrett for sharing that anything else that folks are working on.

A

E

um Just just one other thing to share at least from uh the coveral india folks. I know that they're also exploring the option of adding a cap controller gui using backstage. um So I think it's still still fairly early days, but they're exploring that um and that's just a really really interesting uh initiative.

C

For us in image package, we we already have the pr there, but some people have been asking for and a way to um for the users when they're using image package to select how many times they want to retry.

C

Talking to the registry like if you have a very big bundle that you're trying to copy and it might fail during the process- and it will give more control, so there will be a new flag on image package that will allow the users to select how many times they want image package to try to connect to the registry. uh If something temporary fails. So that's something that some people asked and it should be ready for the next release.

A

Sweet thanks, joelle, okay, any anything else.

A

And there's any discussion topics that folks want to bring to the meeting right now that didn't make it to the agenda.

A

Okay, all right! Well, thank you! Everyone for joining today.

A

If uh you are based in the united states, and you do celebrate thanksgiving, we wish you a happy thanksgiving next week, get stuffed with lots of turkey or whatever you eat on the holiday and we're super thankful to have you part of our carvel community, and we look forward to seeing you at our next meeting, which will be the first thursday of december thanks. Everyone.