Collect requirements for v2.3.0 #14007
Replies: 19 comments 24 replies
-
Do enhancements to the scanning to let users access more security postures of their images. They can include:
@danielpacak / @prahaladdarkin any further comments? |
Beta Was this translation helpful? Give feedback.
-
Introduce rate limitation to replication to handle some environments with limited network bandwidth.
@ywk253100 @bitsf any further comments? |
Beta Was this translation helpful? Give feedback.
-
So far, there are still many API handlers using the ORM transaction with legacy way, which may cause problems (even deadlock) when there are large scale concurrent requests coming in. To improve reliability and consistency, we need to migrate all the APIs using legacy transaction approach to the new model. cc @heww |
Beta Was this translation helpful? Give feedback.
-
Provide one unique API swagger YAML, not two(two YMALs cause problems when automatically generate API clients). cc @reasonerjt, @heww |
Beta Was this translation helpful? Give feedback.
-
How about ship trivy image with a default offline vulnerabilites database. So that it can work in environment without network connection to github. |
Beta Was this translation helpful? Give feedback.
-
Hello all, |
Beta Was this translation helpful? Give feedback.
-
I would like too see some work on Log-Deletion. #14007 proposed the deletion of audit-logs (Background: GDPR) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
规范仓库命名 具体功能如下:
使用场景:
可以规范镜像命名如下:
而不是 :
|
Beta Was this translation helpful? Give feedback.
-
harbor 私有项目单独开放某个镜像仓库的公开权限 场景:
优点:
|
Beta Was this translation helpful? Give feedback.
-
repo proxyset a upstream registry in project setting page global webhookuse to cicd or something. |
Beta Was this translation helpful? Give feedback.
-
Operation statistics, such as image and project statistics, usage statistics, pull counts by user in an interval, etc. |
Beta Was this translation helpful? Give feedback.
-
I would really like the support for more complex (security) policies, which is Imo the main driver for harbor adoption.
|
Beta Was this translation helpful? Give feedback.
-
Better RBAC with a way to define custom roles
|
Beta Was this translation helpful? Give feedback.
-
Add upload and download image (as tar file) option |
Beta Was this translation helpful? Give feedback.
-
Thank you for your guidance, which solved my question!
…------------------ 原始邮件 ------------------
发件人: "goharbor/harbor" ***@***.***>;
发送时间: 2021年3月17日(星期三) 上午10:38
***@***.***>;
***@***.******@***.***>;
主题: Re: [goharbor/harbor] Collect requirements for v2.3.0 (#14007)
@pengkang1991 to the best of my knowledge, image tags are required to uniquely identify a container image and hence hence jdk:v1.11.1 is not the same as jdk:latest.
Hence docker push jdk:v1.11 will not automatically create jdk:latest.
latest is simply a default label applied on images which are pushed in any of the following manner:
docker push jdk or docker push jdk:latest will push the jdk image and create the :latest tag automatically .
However a command like docker push jdk:v1.11 will not create a latest lag - instead an image would be pushed and the v1.11 tag would get created.
You can read this short and informative blog here : https://vsupalov.com/docker-latest-tag/
Note that :latest should be used very careful since it has the capability to introduce unwanted/undesired updates to the docker image.
On that note, I think it would be useful for Harbor UI to display a list of tags available for an image within the registry. @steven-zou does this functionality already exist? I was not able to easily find it in the latest 2.2.0 setup that I have deployed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Beta Was this translation helpful? Give feedback.
-
Important problem to resolve : making exporter work, even with TLS activated. |
Beta Was this translation helpful? Give feedback.
-
Add some endpoint to off-board OIDC user /user in general |
Beta Was this translation helpful? Give feedback.
-
We are in the planning phase for v2.3.0
Please let us know what features you would like to see in the next version!
If there's an issue opened previously for that feature please reference the issue in this discussion!
Beta Was this translation helpful? Give feedback.
All reactions