Cloud Native Computing Foundation Artifact Hub, 10 Nov 2020

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: CNCF Artifact Hub 2020-11-10

Description

CNCF Artifact Hub 2020-11-10

A

A

B

Hello, hello, how are you hey man, good? How are you I'm doing? Okay, I'm doing okay.

C

It's it's a busy time. Okay,.

D

Yeah- and so this is our first meeting without dan.

A

D

So um I don't know about you, I was a bit surprised by it. I didn't realize it would come so quickly.

A

Yeah we didn't need it, it was being all everything so so quick.

D

Yeah yeah from the time of his first test on this to him, passing was less than three months. That's incredibly quick, yeah.

B

D

Wow no problem, we were just getting started um so I know I said I would do uh some blog stuff in the last couple weeks, and so I guess I'll open with that. Since I said I would do stuff, I filed an issue with the cncf on starting a blog and they don't have a recommended method to doing it. It's raised gone everywhere from using hugo as a static site generator to running something on medium, but I have not had a chance to just pick one and get moving on it.

D

Yet I hope to do that maybe next week, because I've been scrambling with some helm stuff.

A

D

Because this friday helm v2 uh it's end of life and the stable and incubator chart repositories are done.

D

Okay, so we've been doing behind the scenes stuff to get ready for that.

A

Yeah I saw that you did you remove the stable and incubate the repos from an artifact hub, yes, okay, yeah. We saw that last friday that we were missing a couple of hundred packages. This must be that.

D

Yes, and- and we we wanted to do that earlier and we had failed to do it to try to motivate people to get their things out, and so that was the scheduled date that we had decided on a couple weeks ago, and so that's just one of the steps.

A

All right, I hope everything goes fine and users just don't find trouble. Moving to the next version.

D

No, no, in fact, we've got a blog post set to go out on friday and that will again point people over to the artifact hub.

A

D

So so that's where it stands. uh I will, though, hopefully starting next week I'll figure out a blogging platform and start crafting some posts to go out.

A

D

A

Yeah, I think that's going to help a lot.

D

Yeah, um because we have.

A

D

Because I really like to get some growth of more people involved in the project, besides just the two of you doing most of the work over this next year to help us be able to go for incubation and moving to other phases, and I realize that the cncf has- I don't know if you know they look like they'll have funding for the next year. For this.

A

Sorry, sorry, can you say it again, please.

D

It looks like the cncf will have funding for everything for this for the next year.

A

D

I don't know if you knew that.

A

No, we didn't so.

D

It looks like it, member renewals and everything are not in yet um it is that season, but they are budgeting and planning and hoping to have all of this funded for the next year. Just like we did.

A

Okay, that's great news: yeah.

D

That's what they're hoping for, of course nothing is done yet, but that's what I just learned okay, but I would still like to see the growth of other people involved in the projects from other organizations and companies, just like other cncf projects have.

A

Yeah, I think that's that's going to be that's going to help a lot to the producer that can keep growing and don't just depend on us. So.

B

And you two have done a great job. Thank you.

D

I've got no complaints.

D

Thank you um and then the other thing I had was the helm hub migration. We talked it out in the helm, one of the helm meetings and we're okay, handing the dns off to you to do that. So at some point you and I can get together and set up the dns from the helm side. So it points over to you.

A

D

Okay, if you're, if we're okay with that, we'll just point it right in artifact hub so artifact hub, can keep control of whatever's going on there.

A

All right, yeah, anytime, so yeah all right.

D

Those were the things that I had did you two have anything.

A

um No, you know we don't usually bring too much stuff to the meeting so but I'll always get asked.

D

Do you have enough to keep you busy for the next couple weeks.

A

Yes, I think so, if not we'll beat you but yeah, we have a few things: spending um yeah, otherwise we'll keep adding more stuff. So it's just. We are starting to forget all the features we have already on board. So that's why your blog is going to help even us. So much.

D

A

We added last week- I don't know if you had a chance to take a look at it. We have added experimental support for oci er, helm repositories, the wedge, support oci, so that now it is possible to even add a oci based reposit health repository to artifada.

B

Oh, that's wonderful,.

A

Yeah, I know you asked us to hold on a bit and but we have been tracking all the issues and we have even seen the pull request. That's actually open, that's seems to be about to be migrated related to the helm, enhance in oh hold on hip six. I think so.

A

D

Share with you that that will change the user experience of somebody interacting with the helm cli, but it won't change well, it will change how things are stored, just because we'll also have a providence file in there. Eventually.

A

Yeah we saw that but say oh most of the stuff shouldn't change so I'll place it here. So how do you add one? It's we have kind of documented it here before yeah we're trying to do that now. Every time we do something we write a piece of.

B

A

Before we forget everything so yeah, it's kind of easy. It's just the same, so you just need to add a repository like you would do normally in the ui. You just not need to prefix it with oci semicolons and it just works. It supports private and non-private repositories and that one actually works with push all the chart versions.

A

We have for active hub to github packages and that one works so fantastic, so yeah, it's kind of cool, and we also mentioned that that was experimental and subject to change as soon as the pending changes in helm were merged.

A

So yeah, there are a few things that we need to think about because stuff, like the verified publisher and the ownership claim that was working from a file that was served. Repository white before.

B

A

Now we don't have such a thing, so there are a few things that we need to think about. Also, I understand that now each of the repositories will only host a single package compared to what we have right now.

D

Yes, with oci it'd be a single package.

A

Yeah, so it might be a bit more of you know some more work for publishers if they have a lot of packages but yeah, I need to find a place to host that that repo white file, or maybe do it somewhere else, some yeah. So a.

B

A

But it's documented so that people know that and the provenance file is already mentioned in that document, so that people know that that's not working yet but we'll get there.

D

All right, no I'm going to add this to the next home meeting to bring it up there.

A

Okay, I reference this yeah the issue in the in this. Let me copy here so that.

D

This would be fun to talk about or bring up just so people know.

A

Yeah we thought that some people might get excited and maybe it helps people on people adopting it earlier. I don't know just I don't know.

C

uh I think this is something josh would like to know too. So. Okay, awesome, oh fantastic! That's great!

C

Thank you. Is there anything else? We should talk about.

A

No, I think, that's it matt.

C

Okay, well, then, uh have a wonderful um week and I'll see you online. Thank you very much. You too, and talk soon talk soon. Bye.

B