FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

• A running Kubernetes cluster (v1.21 or higher is recommended)
• Helm v3.8 or higher for OCI support (Installation instructions)
• kubectl installed and configured

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

Add the Helm chart to your local Helm client.

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

Step 3: Create Namespace

Create a namespace:

kubectl create ns harbor

Save the file below as values.yaml. This configuration enables the Trivy scanner and points all Harbor images to the Minimus registry:

# Matches the port-forward target in Step 6 so Harbor generates correct URLs
externalURL: http://localhost:18080

nginx:
  image:
    repository: reg.mini.dev/harbor-nginx-fips
    tag: latest

portal:
  image:
    repository: reg.mini.dev/harbor-portal-fips
    tag: latest

core:
  image:
    repository: reg.mini.dev/harbor-core-fips
    tag: latest

jobservice:
  image:
    repository: reg.mini.dev/harbor-jobservice-fips
    tag: latest

registry:
  registry:
    image:
      repository: reg.mini.dev/harbor-registry-fips
      tag: latest
  controller:
    image:
      repository: reg.mini.dev/harbor-registryctl-fips
      tag: latest

database:
  internal:
    image:
      repository: reg.mini.dev/harbor-db-fips
      tag: latest

trivy:
  enabled: true
  image:
    repository: reg.mini.dev/harbor-trivy-adapter-fips
    tag: latest

redis:
  internal:
    image:
      repository: reg.mini.dev/harbor-redis-fips
      tag: latest

metrics:
  enabled: true

exporter:
  image:
    repository: reg.mini.dev/harbor-exporter-fips
    tag: latest

Render the chart locally with the overrides to confirm Minimus images will be deployed:

helm template harbor -f values.yaml harbor/harbor | grep "image:" | sort -u

Deploy the Harbor Helm chart with the values.yaml file you saved in the previous step:

helm upgrade --install harbor -f values.yaml harbor/harbor -n harbor

Confirm the Trivy adapter pod is running and ready:

kubectl get pods -n harbor -l component=trivy

Port-forward the core service and trigger a scan via the Harbor API:

kubectl port-forward -n harbor svc/harbor-core 18080:80

Run in another terminal to check the scanner is registered:

curl -s -u admin:Harbor12345 http://localhost:18080/api/v2.0/scanners | python -m json.tool

You should see Trivy listed as the default scanner.

helm uninstall harbor -n harbor
kubectl delete ns harbor

Technical Considerations

The Harbor-Trivy-Adapter-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Terms & Info

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.

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.