harbor

Chart

Data

Updated on October 17

Versions

Browse all available versions of the Helm chart.

Updated

App version

Chart version

Images Included

vulnerabilities

Updated Oct 17, 2026

harbor-exporter v2.15.4

harbor-jobservice v2.15.4

harbor-nginx v2.15.4

harbor-portal v2.15.4

harbor-registry v2.15.4

harbor-registryctl v2.15.4

harbor-trivy-adapter v2.15.4

harbor-valkey v2.15.4

Updated Aug 04, 2026

harbor-exporter v2.15.2

harbor-jobservice v2.15.2

harbor-nginx v2.15.2

harbor-portal v2.15.2

harbor-registry v2.15.2

harbor-registryctl v2.15.2

harbor-trivy-adapter v2.15.2

harbor-valkey v2.15.2

Updated Aug 04, 2026

harbor-exporter v2.15.1

harbor-jobservice v2.15.1

harbor-nginx v2.15.1

harbor-portal v2.15.1

harbor-registry v2.15.1

harbor-registryctl v2.15.1

harbor-trivy-adapter v2.15.1

harbor-valkey v2.15.2

Vulnerabilities

26275113292

harbor 1.19.4
Chart
Data

Updated on October 17

App Version2.15.4

Chart Version1.19.4

Vulnerabilities

Images included

harbor-core v2.15.4

harbor-db v2.15.4

harbor-exporter v2.15.4

harbor-jobservice v2.15.4

harbor-nginx v2.15.4

harbor-portal v2.15.4

harbor-registry v2.15.4

harbor-registryctl v2.15.4

harbor-trivy-adapter v2.15.4

harbor-valkey v2.15.4

Harbor Helm Chart

Harbor is an open source trusted cloud native registry that stores, signs, and scans content. The Harbor Helm chart automates deployment and configuration of Harbor in Kubernetes clusters using Minimus images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges
Persistent storage available in your cluster

Try It Out

In this example we will deploy Harbor on a Kubernetes cluster using the Minimus Harbor Helm chart. Harbor will provide a private container registry with vulnerability scanning, content signing, and access control out of the box.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns harbor

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-harbor oci://helm.mini.dev/harbor \
  --version 1.19.4 \
  -n harbor \
  --wait

If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:

helm install my-harbor oci://helm.mini.dev/harbor \
  --version 1.19.4 \
  -f values.yaml \
  -n harbor \
  --wait

Step 4: Verify Harbor is Running

Confirm the chart deployed successfully and all Harbor components started:

kubectl get pods -n harbor -l app=harbor

You should see output similar to:

NAME                                    READY   STATUS    RESTARTS   AGE
harbor-core-xxxxxxxxx-xxxxx             1/1     Running   0          2m
harbor-database-0                       1/1     Running   0          2m
harbor-jobservice-xxxxxxxxx-xxxxx       1/1     Running   0          2m
harbor-nginx-xxxxxxxxx-xxxxx            1/1     Running   0          2m
harbor-portal-xxxxxxxxx-xxxxx           1/1     Running   0          2m
harbor-redis-0                          1/1     Running   0          2m
harbor-registry-xxxxxxxxx-xxxxx         2/2     Running   0          2m
harbor-trivy-xxxxxxxxx-xxxxx            1/1     Running   0          2m

Step 5: Test HTTP Endpoint

Forward the Harbor NGINX service port to your local machine:

kubectl port-forward svc/my-harbor-nginx 8443:443 -n harbor

In another terminal, verify the Harbor API is responding:

curl -sk https://localhost:8443/api/v2.0/health

You should see a JSON response indicating the health status of each Harbor component.

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-harbor -n harbor
kubectl delete namespace harbor

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.