Upstream
/
harbor
mirror of https://github.com/goharbor/harbor.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Release 1.6.0 (markdown)

Steven Zou 2018-09-12 14:42:43 +08:00
parent d38cfe9610
commit 1932120d75
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Release-1.6.0.md

@ -12,24 +12,32 @@ From V1.6.0, harbor can behavior as a unified cloud-native registry to both serv
* **Overall**:
* Charts are isolated by project namespace
* Access controll is applied to charts by RBAC
* Access control is applied to charts by RBAC
* **User management portal**:
* List all the charts under the specified project namespace with list or card view
* List all the chart versions of one specified chart with list or card view
* Show the details of the specified chart version
- README content and other metatdata information
- README content and other metadata information
- The signature prov file status
- Usage commands reference
- The dependencies of the chart version
- The value file content with key-value view and yaml view
- The value file content with the key-value view and yaml view
* Upload chart w/ prov file
* Download the specified chart version
* Delete the specified chart version
* **Work with Helm CLI**:
* Use `helm repo add` to add harbor as a unified chart repository with specified username, all the project namespaces accessible by that user should be visible to helm.
* Use `helm repo add` to add a harbor project as a separate chart repository, only the charts under that project are visible to helm.
* Use [push](https://github.com/chartmuseum/helm-push) plugin of helm command to push chart to harbor
* Use `helm install` to download the chart from harbor and install it to the target Kubernetes
* Other helm commands like 'helm search' or 'helm verify' are also supported well
### Benefits to users
Cover both image management and helm chart management with one unified powerful cloud-native registry. Avoid spending efforts to introduce a new system in and reduce the system maintenance cost in future. In addition, image and helm chart managements follow the similar user experiences, that will definitely reduce the new system learning efforts. What's more, managing helm charts and images in one system leave enough space and flexibilities for collaborations/integration in the future.
## LDAP group supporting
## Replicate images with label filters