Repolode
Submit
goharbor

goharbor/harbor-helm

Helm chart for deploying the Harbor container registry onto a Kubernetes cluster.

Open-source alternative to:Docker Hub

View on GitHub
Stars
1,532
Forks
869
Open issues
70
Last commit
5 days ago

What is it?

This Helm chart installs Harbor, an open-source container image registry, into a Kubernetes cluster. It is maintained separately from the main Harbor project, so issues about the chart's deployment belong here, while functional questions about Harbor go to the main repository.

The chart lets you choose how Harbor is exposed: Ingress, ClusterIP, NodePort, LoadBalancer, or Gateway API HTTPRoute. TLS can be generated automatically, read from a secret, or left to the ingress controller. Persistence defaults to PersistentVolumeClaims, with options to use an existing claim, a different StorageClass, or external storage for images and charts on Azure, GCS, S3, Swift, or OSS.

The repository documents a high-availability setup and an upgrade guide for existing deployments. Installation requires Kubernetes 1.20 or later and Helm 3.2.0 or later. The master branch is under active development, so stable tagged versions are recommended.

Key features

  • 01Multiple service exposure modes: Ingress, ClusterIP, NodePort, LoadBalancer, and Gateway API.
  • 02Automatic, secret-based, or manual TLS certificate configuration.
  • 03Optional internal TLS between Harbor components.
  • 04Persistent storage via PVC or external object storage (Azure, GCS, S3, Swift, OSS).

Use cases

  • Running a private container registry inside a Kubernetes cluster with Helm.
  • Setting up a highly available Harbor deployment on Kubernetes.
  • Exposing a self-hosted registry through an existing ingress controller or load balancer.

Quick start

  1. 1

    Add the Harbor Helm repository

    helm repo add harbor https://helm.goharbor.io
  2. 2

    Install the chart with release name my-release

    helm install my-release harbor/harbor

Things to know

  • The master branch is in heavy development, so use a stable release instead.
  • Requires a Kubernetes cluster (1.20+) and Helm v3.2.0+.

Topics

#kubernetes#helm#container-registry#docker#devops#helm-chart

FAQ

What is harbor-helm?
Helm chart for deploying the Harbor container registry onto a Kubernetes cluster. This Helm chart installs Harbor, an open-source container image registry, into a Kubernetes cluster. It is maintained separately from the main Harbor project, so issues about the chart's deployment belong here, while functional questions about Harbor go to the main repository.
Is harbor-helm free to use? What license does it have?
harbor-helm is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is harbor-helm still maintained?
Actively maintained. The last commit to harbor-helm was on Oct 16, 2026.
What can I use harbor-helm for?
Running a private container registry inside a Kubernetes cluster with Helm. Setting up a highly available Harbor deployment on Kubernetes. Exposing a self-hosted registry through an existing ingress controller or load balancer.
How do I install harbor-helm?
Add the Harbor Helm repository: helm repo add harbor https://helm.goharbor.io Install the chart with release name my-release: helm install my-release harbor/harbor
Where can I get harbor-helm?
The source code and installation instructions are on GitHub: https://github.com/goharbor/harbor-helm

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects