Project Harbor Community, 7 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CNCF Harbor's Community Zoom Meeting - September 7, 2022

Description

CNCF Harbor's Community Zoom Meeting

A

So hello, everyone welcome to this week's Harbor community meeting today is the 7th September and we can start with our agenda from uh the community meeting URL here and first one is jaolin and he's giving a note about the harbor to six and also plan for two seven.

B

Yeah yeah thanks everybody. uh The first little thing I want to talk about is the 2.6.0 release.

B

uh It is finally cheered in last week and in this release we have introduced a few important feature like uh CV export, and this is asked by Community for a while, I think and another one is the introduce a cage layer to improve the performance artifacts, especially in high components scenario, and this is very useful for the Enterprise Hub instance, where they are very high, concurrent pool and requests and the another one is a purge audio log and uh uh and also we have provided a user guide to use uh velola to backup the harbor M chart so anyway.

B

That is a big achievement for this release. I think and congratulations to the Hubble team and the thanks for all the contributors uh to this release and the next one yeah, that's incubating. You have shown the whole list here: yeah yeah.

A

So I think the the the feature-wise I mean they have like three major features like cash layer was a big feature: CV export audit logs, um but I think the the most impressing one is actually the the fixes. You know how many, how many fixes and updates all this minor uh minor things that we went into so this is really I mean. This was a really big big release.

A

You know to six because there were so many small changes and fixes and updates uh I mean I, I counted them and there was like 100 hundreds over 160. yeah.

B

A

This is a I think, more impressing than um the the new features itself. I mean it's like a big big stability Improvement as well.

C

B

Okay, thank you. Everybody. uh The next. The next item I want to talk about is the 2007 plan. uh Actually, we, a single team, have some initial discussion and with the rodeo and also we have took care of some uh input from the uh Community uh uh discussion and the some issues opened from the community. So we we have achieve the list, um I mean in the comfort in the wiki, and that is something uh what we currently think about. uh We will.

B

We will uh provide it in this release uh under considered that the December is a holiday season, so we may we may uh how to say- and we may include not much as much as the previous release in 2006. So uh this is this is the current issue. We have already labeled with the target, 2.7 and also I.

B

Think there are a few items we will create it later, um based on the uh I mean requirement discussion with the PM Roger so anyway, I think Community can take a look at this and the was a timeline uh about two dollars driven uh as usual. We will have four months release cycle, so we have initial. uh We have an initial timeline uh tentatively, uh maybe in have situated in middle of the December, so for the detail date.

B

I have I, have put it in the wiki, so I'm not going to uh read each of them.

A

Somewhere mid-December yeah yeah.

B

So uh that's a a brief summary of this, so thank you. Everybody.

A

Yeah um yeah and regarding a question regarding the discussions that that there have been on um on on the discussion board, you know for the two celebrities: um did we make a few of those? You know, suggestions from the community into um into to seven so.

B

A

Kind of a feedback loop so that we can say, for example, um yeah, for example, this one from from Alexia, allow you to Links in documentation without version number yeah. This is the from the website, but let's see on on the on the product sums so that we can say hey your requirement.

D

A

Your proposal is now accepted and it's you can track it into this issue. You know, is there? Is there did we? You know kind of a have a few of those things in in.

A

B

Yeah we have some I uh a few items uh coming from the discussion, uh for example and strength. We have a issue, uh maybe two.

B

C

B

Oh okay, I think it's. The other issue is not available.

B

uh Let me open JS 2000 discussion.

C

Yeah I think the.

B

Usual uh uh related to the poor time, update right, I, think that is something Community also want to uh be fixed. It is uh this.

A

B

You mean one: could you scroll down to the bottom.

A

Yeah, this is the button.

B

Yeah I think that is.

B

Yeah, the one four six, three eight.

A

Right yeah so targeted three, two, seven yeah yeah.

B

We will try to fix this in this release. I think this is also important for some of our community users. I think yeah.

C

A

Yeah I mean so you know, so we need to kind of a close close the the loop, because you know we, we ask the people to to provide feedback and if we kind of uh ignoring I mean we have to ignore a few of those things.

A

That's true, but some of them are, you know, good suggestions, and if we have an issue for that, we should link it back, so they that we can see, like you know, we're listening to the users and implementing yeah we're asking for and if it's kind of visible here as a comment you know um we can, we can address that.

A

Okay, um I think from the community. We uh with it to talk about gitpot I'm, just pinging him on.

B

Here I have another thing, he's name showing in the participates.

B

Looks like a probability is not here.

A

I just thinking maybe these joints, but he's online uh and pratik would like to talk about a discussion on this pull request. Let's take a look at this he's. Not there I'll message him in the meantime, so we can.

C

A

A look at this.

C

One and then message him.

A

Okay, um so, but we can take a look anyway um and I think yes, this is the issue here. um I've been looking into this and I would like to get your opinion about. uh So what I think he's trying to do is you know they they're trying to do on-board onboard the user?

A

um So this is what I understand you know, so they they try to onboard the user manually or via API before. Actually it actually locks into Harbor the first time you know so I think this is this is uh his intention.

A

And for that they want to- or he wants to you know, exclude.

C

A

Yeah so for this he wants to exclude the csrf uh csrf uh from uh on board and the question is you know, should we do it? What is what speaks against it?.

D

um But uh what about if the auto on board is disabled communism, the user to unlock a user.

D

To authenticate in the OR at the super wider- and there is another stop in the background- another is the token Exchange and and then at that you're pretty going to the onboard and point um last time if the automobile is disabled, you have to to uh after menu start in the hardware web UI to click, um it's okay, to save on board this user, and then Hardware will write the username on the secret into the Hub database.

D

So that's why we believe that the API supposed not to work for the oitc scenario, um like the comments added by the new in this issue.

D

um So my conscience here is about the uh the user and have you ever tried the.

D

Cli CLR flow with this VR I mean you. You have to build the harbor, which is source code, which is PR and then try to onboard a new user with CLI and to see whether it works or not and like uh what I mentioned. If Hardware enables all the disabled auto on board, the API should not work.

A

But I think they're they're required yeah I mean their requirements because they just called directly the the oedc like you know. So so that's why there is no token before that. So I think he's.

C

Also, explaining.

A

C

D

I, don't I'm not sure whether he tried the horrible other like either end, not just the address of PR for us yeah.

A

Because they know they yeah I mean they're, calling the API directly. You know so they take holding this endpoint to onboard the user via oidc. You know yes,.

D

A

And then do this onboarding.

D

Yeah but uh I need to. uh Why did that this we are um in the oriented back then, but I buy some on when Harvard enables the disabled uh Auto on bar. So how should we handle this kind of situation.

A

Yeah, but so I mean we, we do onboard the users also via uh you know uh this way.

D

A

Know so that's I mean for us. It's also uh relevant. You know to onboard the user directly via API in a sense not to pre-on-board them. You know so that when they come in, they already have the projects assigned and things like this. You know, because if, if you need to have the user on board at first and then you can assign projects to the user, you know, and otherwise you- you cannot do this, and this is you know uh or give them permissions.

A

You know things like this, um and this is what they're doing I guess I mean we do it also in in a similar way.

A

So maybe we can take a look at it. I'm not sure I mean it will not have a negative impact and it will, you know, be uh still be backwards compatible. You know, so that's that's why I'm thinking it if, if there are quite a few people uh asking for that, you should review review this again.

D

A

Because you know it's, it has no negative impact on the on the current state of the application and also on the security I. Think it's not a big issue. If, if this is, uh has uh you know Caesar of skip skipped because normally this is always called first right, yep I mean.

C

A

Okay, um what do we have another topic? um I think we we don't have any other topics on the agenda.

C

A

From yeah from from my site,.

A

um Yeah, maybe someone can approve this pull request. I mean I, um there's a there's a typo here, I mean it is like a really small issue, because the the file name has no markdown extent. No, no markdown ending. You know suffix and that's why it's not correctly displayed in the uh um in.

C

You see like life cycle.

C

A

As you see it's, it's displaying us as a text. You know. So if.

C

A

This correct ending it will display correctly as a markdown. You know like this one properly. So if you approve this request for me, you know, and it needs two approvals, so if someone can approve it quickly and then we can, we have.

C

A

uh Yeah, thank you.

C

A

Okay, otherwise, from from my side, I have no no topics to to discuss anything from from your side um regard, maybe, regarding to seven release, is, is already everything fixed there you know, or is it still kind of a window open for for proposals.

B

Yeah I think we're almost uh we still can evaluate, if other any. If any other things we can uh include um by the way it would expect, uh this can be I mean.

B

I mean uh we will have a expectation in maybe uh panel this month.

C

B

Will I mean we are? We will have a fixed line, so by that time we were not including any additional big features.

C

Okay, yeah yeah, okay,.

D

And also you can a filter issues by label 2.7 to see whatever what we will have in a nasty manner. Yeah.

A

And I mean maybe we have a few contributions as well, that we would like to to contribute.

C

Into seven, that's why um you're welcome foreign.

A

Side- and we have some submittents I- would like to also talk about this one because it's you know coming up a bit more and more, and we have a few discussions. This was already a two and two seven, and this is a proposal from my site. You know how this can be can be done so I need to maybe convert it as a proposal as a official proposal, but it's you know for you to get a kind of understanding, so I mean now we have in two six. We added webassembly module.

A

You know the support representative model, and this was done by you know. uh You know, code contributions or supporting web assembly, the log, the the the icon and things like this, and my idea is because I I see it Harbor moving towards more of a general purpose. Artifact repository, so there's like different types of artifacts stored in Harbor, not only container images and help charts, but also um you know web modules, and we have now different types of web modules.

A

You know so for uh for what web assemblies and and I'm pretty sure, they're going to be much much more in. In the future- um and so my proposal here is, if we can make it a bit more Dynamic so that we can displayed those different artifacts accordingly in in Harbor, maybe we can kind of you know, display it as tabs or maybe we can filter by them.

A

So there's different options, so I just made a proposal with tabs, um but also maybe filter will be proper action, and the idea is that we can kind of configure it dynamically. You know in a sense that whenever there's a new, whatever customer decides artifacts you want to have, he can configure it up front in in Harbor, I know, either via config or via UI.

A

In the context and said, okay I would like to you know, have this artifact type, and then he defines this type and it will be present and it gives a name and it will be present in a UI as a whole Tab, and then you can of course filter it accordingly. So something like this um I think we'll be would be helpful for for Harbor.

A

uh What? What do you think is this something uh well.

E

If, like there are many more incoming tabs and then we will need, then the UI will be kind of like over designed I. Think.

A

Exactly exactly.

E

A

Mean uh one clicks: I mean.

E

Sorry, for example, for like right now, we only have two to call them out there right. One is revolved around the other. One is the help charge yeah, so the the first image out there and the second image there are like four columns um there. If there are like many other tabs in coming, we want to support that uh from the UI perspective it. It looks like over design. For me, like.

A

um I mean the the main goal is that Harbor out of the box will support these two types. You know, but the customer or the user can add other types themselves. You know, so we should more provide a functionality, so that user can add his custom types. You know and those custom types you know can be: maybe a third one or a fourth one or if he has like 20, then of course you will have many tabs.

A

I mean and tabs is just one option, so we can also do it via drop down, but I think.

C

A

Yeah, so if, depending on the on the user, so some will have this type, some will have those types but Harbor out of the box will just support. I would say this two for the beginning. You know and.

E

And the third and the third one for a drop down right.

A

Yeah and then drop down or the user can add his own and then it will be kind of more flexible and then you know it depends on how many how many different types they want to add. But I, don't think users will have you know more than handful, but you know yeah so I mean it's just my proposal, how we can think about extending Harbor for different oci artifacts, because I I'm pretty much sure that we're gonna see much much more artifacts in in the next half a year or year. uh You know popping up.

C

um I think we can I think we just uh ate an option just there to select one type of artifact to display, for example, I just want to display all the container images or the time chart or the R Us or other Watson artifact, like that one user, exactly just the click that is artifact then only display this artifact as.

A

A test exactly.

E

Yeah that's well, but the disadvantage of that event is that the user can only display one type of the artifact right. If the user want to display two two tabs, then then you.

D

E

Not be able to do that right.

D

um So my opinion for from for your uh UI ux design, is since that it starts originally because that, uh in the top level we should help a repository or not rather than the containers, hampshires and the hours of Etc, um because that any specific repository we can have different kinds of artifacts like image I'm charged.

D

But if you put the charge um almost here, um let's break the top from up to down on on design of of uh artifact, and and in addition to that, um so now we are planning to duplicate a train museum. So we definitely will only have one type of uh repository. It's very still not have charts list in uh project and and that's also a.

A

D

But yeah this is the particular for the Hampshire I'm, not sorry for the Champions, and so we will put all the uh oci contact for artifacts into repositories. So um we have a filter for artifact, like you can select type equals or hours to filter out your uh artifacts I believe this is enough for the user to filter your artifacts I demand for that to you should put um the type in in the UI is not reasonable.

E

So yeah, do you mean we only need one column called repository and all the artifacts are listed in the repositories there right and then we can add an additional future. On top of the repository to filter which type of artifacts the user want to display right right. We.

D

Have it's not additional feature? We already.

E

D

Yeah, okay, so The Current Designs. We put all the things into the password, because that n is specific. Artifact real belong to one repositors so and then and any sophistic repository. You can filter your artifacts by by type.

C

D

Should be able to filter.

A

C

D

No, no so I'm not sure sorry.

A

C

Is currently version it.

E

Looks like there's no filter against.

E

We only have a feature against the name.

A

D

A

Is two five.

C

A

I have an artifact yeah.

C

No go back to this page yeah, and this page there is a search: oh okay, push it back.

C

You need to click the repository and.

C

Click the new pattern yeah and they are they're such.

C

E

C

I think we should uh filter the repository based on the artifact that it contains, for example, it is if.

D

C

A lot effect, then, you will only display the reportery, which has uh was an artifact okay,.

D

Yeah, we are maintaining the list of time here. So, if I, if we decide to expand Harbor to support any external type of attack, when you add it into the cut list so that the user can list the artifacts by and discuss.

C

I suggested to move this uh search condition into the upper level yeah. No, the repository level yeah.

A

I haven't I, haven't.

C

Seen epic sample here somewhere and I cannot find it. Sorry.

D

So maybe we should uh um have some tips for search. Okay, I may not know how to search my time.

D

So you can. You can just uh file an issue or not, and we will have the UI designer to to reveal your issue, and maybe you can do something hazard.

E

But you have that you mean we move the search.

D

No, we just uh I my opinion, just remark: we can just ask a true tip to tell user how to search by time. Okay,.

C

Or filter by type yeah.

A

Okay yeah. This would, of course, help a bit yeah. um This would definitely help at search by type.

A

But it should I think it should be on level up and I'm, not sure I think it should be one level up.

E

Yeah I I I agree with.

A

That, because, when I, when I, for example, push a help chart, you know I have already a Helm chart as a um as an as an artifact there and I cannot filter by this artifact, because everything inside this this this artifact is a Helm chart. I mean I. Can I can show this here, I think it makes it clear. These are positive, so this is. This is, for example, a Helm chart here inside right.

A

So if I, if I take a look so now like this old Helm charts, it makes no sense to filter it, because I can only have health charts here. I cannot have images here, I mean. Maybe I can push images here as well, but but normally uh it's just something. You.

D

Can put um you can put everything into once before yeah? You can put the help chart into a reporter a, and you can also put a image image to that reporter. So in this situation you can use type to filter, really wrong: okay, so yeah. So if you uh uh yeah.

C

D

Filter, uh so the filter here should only filter for recording not for the artifact.

C

C

A

Okay, okay, interesting I, didn't know this existed, um um but thanks yeah, so it makes not This functionally Not That pressing. You know having having it this way, but but good to know. um Yeah. Thank you for clarification. I think we will maybe help to uh document it somehow or make it more usable or present present for the user too. So he knows yeah.

A

um Okay from me from my side, I think there is uh I, have no questions. Oh no, there's no discussion points from your side.

A

I guess not all right, um then I would say. Thank you very much for your time and have a nice have a nice evening.

A

B

You bye, everyone bye, see you next time.