harbor-exporter-iamguarded

Chainguard Container for harbor-exporter-iamguarded

Harbor - Iamguarded variant

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/harbor-exporter-iamguarded:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Overview

Harbor Iamguarded is a security-enhanced variant of Harbor, an open source cloud native registry that stores, signs, and scans container images. This image and chart combination provides additional security benefits over standard Harbor deployments, with all components using Chainguard's security-hardened container images with minimal attack surface.

This image provides the following Harbor components:

The accompanying Iamguarded Helm chart (iamguarded-harbor) also includes these supporting images:

• nginx-iamguarded
• redis-iamguarded
• postgres-iamguarded
• os-shell-iamguarded

Helm Chart Installation

The Harbor Iamguarded Helm chart is delivered exclusively through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/harbor

Basic Installation

Once authenticated (see below) you can install the chart with standard Helm commands and your organization name:

helm install harbor oci://cgr.dev/$ORGANIZATION/iamguarded-charts/harbor \
  --set "global.org=$ORGANIZATION"

Important: Replace $ORGANIZATION with your Chainguard organization name. The default organization in the chart values is chainguard-private, which must be changed to match your organization.

Configuration Requirements

Organization Setting

The global.org value is required and can be set either:

• Via --set flag during installation
• In your existing values.yaml file

Registry Configuration

For users who mirror images to custom repositories:

• Use global.imageRegistry to override the default cgr.dev
• For complex mirroring strategies, consult the chart's values.yaml for individual image configuration options including registry, repository, tag, and digest

Example values.yaml for individual image configuration:

# Harbor Core image
core:
  image:
    registry: myregistry.example.com
    repository: mirrored/harbor-core-iamguarded
    digest: sha256:... # Use specific digest instead of tag

# Harbor Registry image
registry:
  server:
    image:
      registry: myregistry.example.com
      repository: mirrored/harbor-registry-iamguarded
      digest: sha256:...
  controller:
    image:
      registry: myregistry.example.com
      repository: mirrored/harbor-registryctl-iamguarded
      digest: sha256:...

# Harbor Portal image
portal:
  image:
    registry: myregistry.example.com
    repository: mirrored/harbor-portal-iamguarded
    digest: sha256:...

# Harbor Jobservice image
jobservice:
  image:
    registry: myregistry.example.com
    repository: mirrored/harbor-jobservice-iamguarded
    digest: sha256:...

# Trivy Adapter image
trivy:
  image:
    registry: myregistry.example.com
    repository: mirrored/harbor-adapter-trivy-iamguarded
    digest: sha256:...

# Harbor Exporter image
exporter:
  image:
    registry: myregistry.example.com
    repository: mirrored/harbor-exporter-iamguarded
    digest: sha256:...

Authentication

For detailed instructions on configuring authentication and pull credentials for iamguarded images, please refer to our comprehensive guide:

How to Use Chainguard Helm Charts

Best Practices

1. Pin to Digest: While charts follow the same tagging scheme as Chainguard images, always pin to a specific chart digest to prevent unexpected updates:

   helm install harbor oci://cgr.dev/$ORGANIZATION/iamguarded-charts/harbor@sha256:DIGEST \
     --set "global.org=$ORGANIZATION"

   The digest can be found in the output of helm pull e.g:

   helm pull oci://cgr.dev/$ORGANIZATION/iamguarded-charts/harbor
   Pulled: cgr.dev/ORGANIZATION/iamguarded-charts/harbor:VERSION
   Digest: sha256:6471bd888adc895c4c8d259fd72ae7d165da585208bf5670228319c8c0872a49

   Digest value for illustrative purposes only.

2. Review Default Values: The chart provides security-minded defaults that are sensible but may not be production-ready for all use cases. Review the chart's values.yaml (run helm show values) for the full range of configuration options.

3. Image Pinning: All Iamguarded charts pin images to specific digests that have been tested for compatibility, ensuring reliable deployments.

Validation

After deployment, validate your Harbor Iamguarded installation using standard Harbor verification methods. The deployment functions as a standard Harbor instance, so all typical Harbor validation procedures apply.

Prerequisites

Prerequisites are defined in the chart's Chart.yaml and individual templates. No additional requirements beyond standard Kubernetes and Helm functionality are needed.

Security Considerations

The Harbor Iamguarded chart provides security-minded defaults while acknowledging the cluster-specific nature of both Harbor and Kubernetes environments. Review and adjust settings based on your specific security requirements and cluster configuration.

For detailed configuration options and advanced usage, refer to the chart's values.yaml file.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.