Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-12-18 14:47:38 +01:00
Code Issues Projects Releases Wiki Activity
An open source trusted cloud native registry project that stores, signs, and scans content.
8,084 Commits 56 Branches 319 Tags 338 MiB
Go 54.3%
TypeScript 20.4%
HTML 8.3%
Python 5.8%
RobotFramework 5.5%
Other 5.6%
1698cc034a
Go to file
Danfeng Liu (c) 1698cc034a Add a replication scope keyword for waiting the completion fo replication result. All replication test case must use this keyword to verify if image was pulled. 
Signed-off-by: Danfeng Liu (c) <danfengl@vmware.com>
2019-11-27 15:51:03 +08:00
.github Update config file names 2019-09-02 18:19:06 +08:00
API feat(vuln-severity): map negligible to none to match CVSS v3 ratings (#9885) 2019-11-18 14:36:51 +08:00
contrib Update config file names 2019-09-02 18:19:06 +08:00
docs Remove scripts to deploy Harbor on k8s 2019-11-11 19:23:22 +08:00
make Merge pull request #9964 from heww/fix-clair-updaters-disable 2019-11-22 13:38:34 +08:00
src Update minimum length of project name 2019-11-26 12:41:51 +08:00
tests Add a replication scope keyword for waiting the completion fo replication result. All replication test case must use this keyword to verify if image was pulled. 2019-11-27 15:51:03 +08:00
tools build(scanner-adapter): bump up clair adapter to v1.0.1-rc2 2019-11-13 02:35:21 +00:00
.dockerignore Add dockerignore file to prevent local node_modules to be copied into the portal image 2019-05-18 09:11:35 +02:00
.drone.yml There is a new commit in harbor-e2e-engine:1.42, which is upgrade docker to the latest version, so drone.yml should be update to the new one. 2019-11-19 15:03:04 +08:00
.gitignore Add immutable tag in project detail 2019-10-18 11:28:39 +08:00
.gitmessage Update README and .gitmessage 2018-07-17 16:42:03 +08:00
.travis.yml Bump up golang to 1.12.12 2019-10-21 15:55:58 +08:00
ADOPTERS.md Merge pull request #9534 from zhill/add_anchore_adopter 2019-10-23 20:49:39 +08:00
CHANGELOG.md Update CHANGELOG.md for v1.8.0 2019-06-04 11:20:28 +01:00
CONTRIBUTING.md add coding style documentation 2019-11-21 13:53:54 +08:00
gskey.sh.enc Enable travis to update logs to GSR (#5949) 2018-09-27 08:54:56 +08:00
LICENSE Replacing copyright notices with "Copyright Project Harbor Authors". 2018-09-19 16:59:36 +00:00
Makefile udpate base image to 1.10.0 2019-11-22 16:47:32 +08:00
OWNERS.md Update OWNERS.md 2019-10-21 02:34:09 -05:00
README.md remove the KubeCon San Diego event preview section 2019-11-26 17:42:14 +08:00
RELEASES.md Document the versioning and release process, also updating the SECURITY.md 2019-10-18 14:24:42 +08:00
ROADMAP.md Update ROADMAP.md 2019-10-22 11:16:09 -07:00
SECURITY.md Document the versioning and release process, also updating the SECURITY.md 2019-10-18 14:24:42 +08:00
VERSION Bump up version to v1.10 2019-10-19 01:19:13 +08:00

README.md

Harbor

Build Status Coverage Status Go Report Card CII Best Practices Codacy Badge Nightly Status


notificationCommunity Meeting
The Harbor Project holds bi-weekly community calls in two different timezones. To join the community calls or to watch previous meeting notes and recordings, please visit the meeting schedule.



Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get a stable set of binaries.

Harbor

Harbor is an open source trusted cloud native registry project that stores, signs, and scans content. Harbor extends the open source Docker Distribution by adding the functionalities usually required by users such as security, identity and management. Having a registry closer to the build and run environment can improve the image transfer efficiency. Harbor supports replication of images between registries, and also offers advanced security features such as user management, access control and activity auditing.

Harbor is hosted by the Cloud Native Computing Foundation (CNCF). If you are an organization that wants to help shape the evolution of cloud native technologies, consider joining the CNCF. For details about who's involved and how Harbor plays a role, read the CNCF announcement.

Features

  • Cloud native registry: With support for both container images and Helm charts, Harbor serves as registry for cloud native environments like container runtimes and orchestration platforms.
  • Role based access control: Users and repositories are organized via 'projects' and a user can have different permission for images or Helm charts under a project.
  • Policy based replication: Images and charts can be replicated (synchronized) between multiple registry instances based on policies with multiple filters (repository, tag and label). Harbor automatically retries a replication if it encounters any errors. Great for load balancing, high availability, multi-datacenter, hybrid and multi-cloud scenarios.
  • Vulnerability Scanning: Harbor scans images regularly and warns users of vulnerabilities.
  • LDAP/AD support: Harbor integrates with existing enterprise LDAP/AD for user authentication and management, and supports importing LDAP groups into Harbor and assigning proper project roles to them.
  • OIDC support: Harbor leverages OpenID Connect (OIDC) to verify the identity of users authenticated by an external authorization server or identity provider. Single sign-on can be enabled to log into the Harbor portal.
  • Image deletion & garbage collection: Images can be deleted and their space can be recycled.
  • Notary: Image authenticity can be ensured.
  • Graphical user portal: User can easily browse, search repositories and manage projects.
  • Auditing: All the operations to the repositories are tracked.
  • RESTful API: RESTful APIs for most administrative operations, easy to integrate with external systems. An embedded Swagger UI is available for exploring and testing the API.
  • Easy deployment: Provide both an online and offline installer. In addition, a Helm Chart can be used to deploy Harbor on Kubernetes.

API

  • Harbor RESTful API: The APIs for most administrative operations of Harbor and can be used to perform integrations with Harbor programmatically.
  • Scanner Open API: This API must be implemented in order to register a new artifact scanner in Harbor registry.

Install & Run

System requirements:

On a Linux host: docker 17.06.0-ce+ and docker-compose 1.18.0+ .

Download binaries of Harbor release and follow Installation & Configuration Guide to install Harbor.

If you want to deploy Harbor on Kubernetes, please use the Harbor chart.

Refer to User Guide for more details on how to use Harbor.

Community

Additional Tools

Tools layered on top of Harbor and contributed by community.

  • Harbor.Tagd
    • Automates the process of cleaning up old tags from your Harbor container registries.
    • Lead by @nlowe from HylandSoftware.

Demos

  • Live Demo - A demo environment with the latest Harbor stable build installed. For additional information please refer to this page.
  • Video Demos - Demos for Harbor features and continuously updated.

Partners and Users

For a list of users, please refer to ADOPTERS.md.

License

Harbor is available under the Apache 2 license.

This project uses open source components which have additional licensing terms. The official docker images and licensing terms for these open source components can be found at the following locations: