goharbor/harbor-helm

The helm chart to deploy Harbor

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on April 7th, 2021
Created on August 20th, 2018
Open Issues & Pull Requests: 72 (+0)
Number of forks: 862
Total Stargazers: 1,511 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 45.8 days
90th percentile: 21.0 days
Tracked items: 221

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 6% of issues opened in the past year have been closed. Three people close 50% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 367 days
Stale 30+ days: 22
Stale 90+ days: 12

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 3

Top labels

  • Stale (114)
  • kind/requirement (21)
  • needs/follow-up (20)
  • help wanted (18)
  • pending-for-more-info (13)
  • backlog (12)
  • env/tools/argocd (9)
  • target/1.18.0 (4)

Detailed Description

Harbor-helm is the official Helm chart repository for deploying Harbor, a cloud-native container registry and artifact management platform, into Kubernetes clusters. The repository serves as the primary deployment mechanism for Harbor using Helm, the Kubernetes package manager, and is written primarily in Mustache templating language. According to the README, the repository explicitly focuses on chart deployment via Helm, while functionality issues and Harbor-specific questions are directed to the main goharbor/harbor repository.

The chart supports Kubernetes clusters version 1.20 and above with Helm v3.2.0 or later. Harbor-helm provides multiple configuration options for exposing the Harbor service within Kubernetes environments, including Ingress, ClusterIP, NodePort, LoadBalancer, and Gateway APIs. Each exposure method serves different deployment scenarios, from internal cluster access via ClusterIP to external cloud provider load balancers. The chart allows users to configure the external URL for Harbor's core service, which is used to populate Docker and Helm commands displayed in the portal and to generate token service URLs returned to Docker clients.

Data persistence is a configurable aspect of the deployment, with options to disable persistence entirely, use Persistent Volume Claims with dynamic provisioning through a default StorageClass, or leverage external storage solutions. For images and charts specifically, the chart supports external storage backends including Azure, Google Cloud Storage, Amazon S3, Swift, and Alibaba OSS. This flexibility enables organizations to integrate Harbor with their existing cloud infrastructure and storage solutions.

The repository maintains active development and community engagement.

The repository is classified across multiple domains including DevOps tools, container registry, Kubernetes integration, software distribution, secure storage, security compliance, image scanning, role-based access control, deployment automation, and artifact management.

The README explicitly notes that the master branch is in heavy development and recommends using stable versions instead. The chart includes documentation for high availability deployments and upgrade procedures. Users are encouraged to contribute to the project through the established contribution guidelines. The chart's configuration is highly customizable through command-line flags or direct editing of the values.yaml file, allowing organizations to tailor Harbor deployments to their specific infrastructure and security requirements.