Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-11-26 12:15:20 +01:00
Code Issues Projects Releases Wiki Activity
An open source trusted cloud native registry project that stores, signs, and scans content.
6,417 Commits 53 Branches 317 Tags 334 MiB
Go 54.3%
TypeScript 20.4%
HTML 8.2%
Python 5.8%
RobotFramework 5.5%
Other 5.7%
1fdc2e6ba9
Go to file
Daniel Jiang 1fdc2e6ba9 Provide API to generate CLI secret 
This commit provide an API to allow a user that is onboarded via OIDC
authn update his CLI secret.

Signed-off-by: Daniel Jiang <jiangd@vmware.com>
2019-04-22 13:34:12 +08:00
.github Add items to exemptlabels in stale.yml (#7058) 2019-03-05 10:52:44 +08:00
contrib Clean up the contrib folder 2018-09-10 20:37:32 +08:00
docs Provide API to generate CLI secret 2019-04-22 13:34:12 +08:00
make Provide API to generate CLI secret 2019-04-22 13:34:12 +08:00
src Provide API to generate CLI secret 2019-04-22 13:34:12 +08:00
tests Merge pull request #7326 from ninjadq/default_config_to_https 2019-04-22 09:24:39 +08:00
tools Merge pull request #6755 from ninjadq/refactor_prepare 2019-03-22 14:54:30 +08:00
.drone.yml Update import path in go code 2018-08-23 17:50:53 +08:00
.gitignore Merge remote-tracking branch 'upstream/master' into 190311_sync 2019-03-11 20:34:49 +08:00
.gitmessage Update README and .gitmessage 2018-07-17 16:42:03 +08:00
.travis.yml Remove the E2E test cases for replication 2019-04-12 17:37:14 +08:00
ADOPTERS.md Updating ADOPTERS.md 2018-10-16 09:24:48 -04:00
CHANGELOG.md Update CHANGELOG.md to make it up to date (#7315) 2019-04-09 12:27:47 +08:00
code-of-conduct.md Leveraging CNCF's Code of Conduct 2018-09-27 12:11:07 -04:00
CONTRIBUTING.md add new version info for contributing guide 2019-03-29 14:12:52 +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 Patch regsitry v2.7.1 with fix on distribution issue 2819 2019-04-09 18:42:29 +08:00
OWNERS.md Add new two maintainer Fanjian Kong & Mingming Pei 2019-03-11 14:40:46 +08:00
README.md Harbor project contact information updated 2019-03-07 12:30:11 -05:00
ROADMAP.md update documents (#2020) 2017-04-17 13:46:39 +08:00
VERSION Promte version on master to v1.8.0 2019-01-09 17:41:47 +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, to join them and watch previous meeting notes and recordings, please see 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 stable binaries.

Harbor

Harbor is an 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 under a project.
  • Policy based image replication: Images can be replicated (synchronized) between multiple registry instances based on policies with multiple filters (repository, tag and label). Harbor will auto-retry to replicate 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.
  • 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.
  • Easy deployment: Provide both an online and offline installer.

Install & Run

System requirements:

On a Linux host: docker 17.03.0-ce+ and docker-compose 1.10.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: