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. GitGenius activity tracking shows a median issue and pull request response latency of 70.1 hours across 227 items, with a mean latency of 370.0 hours, indicating variable response times depending on issue complexity. The most frequently applied issue labels are Stale with 98 occurrences, kind/requirement with 21, and needs/follow-up with 19, suggesting ongoing maintenance and feature request management. The most active contributors tracked by GitGenius are MinerYang with 310 events, reasonerjt with 101 events, and zyyw with 60 events, demonstrating concentrated maintainer involvement.
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. It shares overlapping contributors with goharbor/harbor, argoproj/argo-cd, and kubernetes/website, indicating integration within broader Kubernetes and CI/CD ecosystems.
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.
