Installing the chart

Prerequisites

• Kubernetes 1.25+
• Helm 3.6+
• The trust source namespace must exist before install (defaults to cert-manager)

Installation steps

All examples in this guide use the public chart and images. If you've mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored chart instead of the public one.

For example:

• Public chart: dhi.io/<repository>:<tag>
• Mirrored chart: <your-namespace>/dhi-<repository>:<tag>

For more details about customizing the chart to reference other images, see the documentation⁠.

Step 1: Optional. Mirror the Helm chart and/or its images to your own registry

To optionally mirror a chart to your own third-party registry, you can follow the instructions in How to mirror an image ⁠ for either the chart, the image, or both.

The same regctl tool that is used for mirroring container images can also be used for mirroring Helm charts, as Helm charts are OCI artifacts.

For example:

 regctl image copy \
     "${SRC_CHART_REPO}:${TAG}" \
     "${DEST_REG}/${DEST_CHART_REPO}:${TAG}" \
     --referrers \
     --referrers-src "${SRC_ATT_REPO}" \
     --referrers-tgt "${DEST_REG}/${DEST_CHART_REPO}" \
     --force-recursive

Step 2: Create a Kubernetes secret for pulling images

The Docker Hardened Images that the chart uses require authentication. To allow your Kubernetes cluster to pull those images, you need to create a Kubernetes secret with your Docker Hub credentials or with the credentials for your own registry.

Follow the authentication instructions for DHI in Kubernetes⁠.

For example:

kubectl create secret docker-registry helm-pull-secret \
  --docker-server=dhi.io \
  --docker-username=<Docker username> \
  --docker-password=<Docker token> \
  --docker-email=<Docker email>

Step 3: Install the Helm chart

Create the trust source namespace if it does not already exist (default is cert-manager), then install the chart. Make sure you use helm login to log in before running helm install. Optionally, you can also use the --dry-run flag to test the installation without actually installing anything.

By default the chart expects cert-manager to issue the webhook TLS certificate. For a quick start without cert-manager, enable Helm-managed webhook certificates with --set app.webhook.tls.helmCert.enabled=true (not recommended for production).

kubectl create namespace cert-manager --dry-run=client -o yaml | kubectl apply -f -

helm install my-trust-manager oci://dhi.io/trust-manager-chart --version <version> \
  --namespace cert-manager \
  --set "imagePullSecrets[0].name=helm-pull-secret" \
  --set "app.webhook.tls.helmCert.enabled=true"

Replace <version> accordingly. If the chart is in your own registry or repository, replace dhi.io with your own registry and namespace. Replace helm-pull-secret with the name of the image pull secret you created earlier.

Step 4: Verify the installation

The deployment's pods should show up and running almost immediately:

$ kubectl get pods -n cert-manager -l app.kubernetes.io/name=trust-manager-chart
NAME                                    READY   STATUS    RESTARTS   AGE
trust-manager-chart-xxxxxxxxxx-xxxxx    1/1     Running   0          30s