Collect requirements/idea/features for v2.7.0 #16775
Replies: 22 comments 19 replies
-
|
We would appreciate a working API concept where "normal" users and robot accounts/technical users can make automated API calls to Harbor
|
Beta Was this translation helpful? Give feedback.
-
|
Enable that e.g. projects/repositories can be opened in a new browser tab |
Beta Was this translation helpful? Give feedback.
-
|
Would it be poasible to add user federation concept to harbor where you could use something like girhub federated identity to login? |
Beta Was this translation helpful? Give feedback.
-
|
Would it make sense to integrate that directly into Harbor or use Keycloak as an OIDC provider for Harbor, and let Keycloak handle the bridging to external ID providers (Google, GitHub, etc.)? |
Beta Was this translation helpful? Give feedback.
-
|
A few for now, might have some more ideas later:
|
Beta Was this translation helpful? Give feedback.
-
|
CVE data exporting feature is on process goharbor/community#174 |
Beta Was this translation helpful? Give feedback.
-
|
Just for convenient reasons:
Example: Example from Tanzu: |
Beta Was this translation helpful? Give feedback.
-
|
I was thinking the same in the past, and that is not related to the release anyway :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for pointing this out! |
Beta Was this translation helpful? Give feedback.
-
|
It seems that https://goharbor.io/docs will be automatically redirected to the latest version of doc, for example https://goharbor.io/docs/2.5.0, while subpages will not be redirected, for example https://goharbor.io/docs/administration/configure-proxy-cache/ will not be redirected and report 404. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I know harbor has geo-replication feature, but it is currently replicating only the repositories. whatever goes to database like users, projects. quota's etc are not replicated. We use postgres streaming replication to remote site, but the local harbor-core instances requires a WRITABLE DB on a read-only postgres replica pod, which is not possible unless it got promoted to master mode. It possible to have active-standby across DC-DR sites, so everything gets replicated across sites. In this case, we don't have to rely on DB replication. DB can be updated using harbor replication feature beyond registry replication? |
Beta Was this translation helpful? Give feedback.
-
|
I would like to see some improvements regarding the API. When you work with the API a lot of things only make sense in the frontend's context and hence a designed like this. There are quite a few issues around already. I plan to create a summarizing issue or start a discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Please so. The API should serve the UI, but design should be API-first. |
Beta Was this translation helpful? Give feedback.
-
|
Working webhook integration between Harbor and Mattermost. Currently, Harbor is not able to send a message to Mattermost because the format of the message is wrong (for Mattermost). |
Beta Was this translation helpful? Give feedback.
-
|
From the UX/DX point of view and considering the bigger role of OCI artifacts in the Cloud Native ecosystem. There are ton of projects already using OCI registries to store other artifacts then container images, eg. ORAS, Helm OCI, Singularity, ML Data Models and so on. At the Moment we only have two groups/tabs My proposal for Harbor 2.7 is that we should extend Harbor in a way that the user can decide on a project basis what groups he wants to see. There should be a default list in the project like Containers, Helm Chart and OCI Artifacts but the user should be able to change that according to the image metadata.
The results would be that an ML team could config their project to only see ML Data to TF and the software engineering team would be fine with the defaults. |
Beta Was this translation helpful? Give feedback.
-
|
I would like to have the option to add a banner where I can add some information (e.g. maintenance information,...). It could look like this:
|
Beta Was this translation helpful? Give feedback.
-
|
This would be a big help for managing an instance for multiple client teams. I'd love to take it a step further. Add:
|
Beta Was this translation helpful? Give feedback.
-
|
Hello, it would be nice to have Trivy metrics about CVE in artifacts to integrate them with prometheus + grafana. |
Beta Was this translation helpful? Give feedback.
-
|
I'd hope that this wouldn't be Trivy-specific, but something gathered through the Harbor Scanner API. My install uses Anchore and the Harbor Anchore Scanner Adapter. |
Beta Was this translation helpful? Give feedback.
-
|
this one looks must have #17125 @dkulchinsky |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @OrlinVasilev, would very much to like to see this being implemented. This becomes especially important for scaling Harbor and still being able to efficiently scan for vulnerabilities stored images. I think this may indirectly depend on #14638 getting fixed, which seems like there's some possible fix inflight 🤞🏼 🙏🏼 |
Beta Was this translation helpful? Give feedback.
-
|
Yep this looks like a good call. |
Beta Was this translation helpful? Give feedback.
-
|
looks like this won't make into 2.7 afterall #17125 (comment) 😞 but hopefully still on track for 2.8 🙏🏼 |
Beta Was this translation helpful? Give feedback.
-
The image is too big nowWith the upgrade of the go version and the addition of functions, the image is also getting larger。
|
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use the following means
|
Beta Was this translation helpful? Give feedback.
-
|
UPX have quite a few disadvantages, I would rather shrink the package and image size. Here are some other methods reduce the size: https://github.com/xaionaro/documentation/blob/master/golang/reduce-binary-size.md |
Beta Was this translation helpful? Give feedback.
-
|
thanks |
Beta Was this translation helpful? Give feedback.
-
|
Configurability/standardization of password requirements Currently:
For the sake of consistency and security, can we please:
|
Beta Was this translation helpful? Give feedback.
-
|
@sfgets please add your label rework thoughts here :) Thanks ! |
Beta Was this translation helpful? Give feedback.
-
|
With docker not being supported on RHEL 8+ hosts, I think it would be nice to be able to setup harbor on podman (manually or by using ansible). I know that it shouldn't be that hard, because I am currently working on an ansible playbook and it works (only notary is having issues). It would be nice to see it as an official way to install harbor on nodes running podman as container management. Please also see my Q&A regarding this topic (#17268 (comment)) |
Beta Was this translation helpful? Give feedback.
-
|
I added a couple questions/ideas to #17268; please take a look and see if these solutions might work. |
Beta Was this translation helpful? Give feedback.
-
|
logging format requirement: right now Harbor use it's own log library, src/lib/log/* could consider to use open source logging library like "github.com/Sirupsen/logrus" or, as Harbor use beego, could use its log as well: then it will be easy to provide more log options, like json format, out put to file/socket endpoint, like https://docs.docker.com/registry/configuration/#log |
Beta Was this translation helpful? Give feedback.
-
|
I'd REALLY like to see Harbor admins be able to disable the ability to set projects 'public' on a per-project level (see #12306) The really nice thing about Harbor is that we are able to offer stuff in a self-service way to our teams by giving out project admin rights to certain subgroups of users. But the fact that they can accidentally or otherwise click a button and set their project to be fully public, no auth required to pull images, is super scary. We'd really like the ability to turn it off, and I think the lack of ability to be able to do so is probably a blocker for some organisations looking to adopt Harbor |
Beta Was this translation helpful? Give feedback.
-
|
the 'project' level switch is the minimum I'd like to be able to disable, all the other suggestions in #12306 are also very relevant |
Beta Was this translation helpful? Give feedback.
-
|
This is also an issue we'd really like to see fixed - #14638 We do daily scans with Trivy, but this resets 'last pull' so retention policies based on time since last pull are just broken, meaning we can't do automatic removal of old / unused images. It's a pretty old issue as well, so it'd be great to see it get picked up and fixed. |
Beta Was this translation helpful? Give feedback.
-
|
big +1 on that and I think it would be critical to enable #16775 (comment) (as I mentioned there as well) |
Beta Was this translation helpful? Give feedback.
-
|
Cleaning the technical tables in postgres or more interesting add some harbor parameters to schedule cleaning actions (cron + how many we keep) linked here https://github.com/goharbor/harbor/issues/17538 |
Beta Was this translation helpful? Give feedback.
-
|
I think gaps in GC have to be addressed there's a story from last year #16010 listing the main issues, some low hanging fruit items were addressed. However from our experience, GC becomes mostly useless in large scale deployments of Harbor. Specifically, with the following issues that need to be addressed:
some of these issues are 2+ years old, especially #12948 which in our case results in GC being able to clean only ~200 artifacts in 24 hours, while we have >170,000 artifacts in the thrashed queue. |
Beta Was this translation helpful? Give feedback.
-
|
/cc @Vad1mo |
Beta Was this translation helpful? Give feedback.
-
|
we still see problems popping up with GC. |
Beta Was this translation helpful? Give feedback.
-
|
Optimize the push image processing logic when the quota is full. #17390 |
Beta Was this translation helpful? Give feedback.
-
Hello Community,
as we released v2.5 and we have plan and roadmap for v2.6 it's time to brainstorm the ideas and requirements for the feature list for 2.7!
Please share your thoughts here so we can all work on proper roadmap and achieving it!
Keep in mind that Harbor is community developed and driven project so not everything can be implemented right away :)
If you have an idea or need and eager to work on, we will support you and help you get there!
Thank you being essential part of the community!
Orlix
Harbor Community Manager
Beta Was this translation helpful? Give feedback.
All reactions