Installing the chart

Prerequisites

• Kubernetes 1.21+ (recommended 1.30+)
• Helm 3.8+

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

To install the chart, use helm install. 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.

helm install my-kured oci://dhi.io/kured-chart --version <version> \
  --set "image.pullSecrets[0].name=helm-pull-secret"

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.

By default, this chart configures kured with rebootMethod: signal and grants the KILL capability instead of using the upstream default (rebootMethod: command). This allows the container to run as a non-root user without requiring elevated privileges.

If you need to use the upstream default reboot method (e.g. because your environment requires it), you can override these settings:

helm install my-kured oci://dhi.io/kured-chart --version <version> \
  --set "image.pullSecrets[0].name=helm-pull-secret" \
  --set "configuration.rebootMethod=command" \
  --set "containerSecurityContext.capabilities.add={SYS_BOOT}" \
  --set "containerSecurityContext.runAsNonRoot=false" \
  --set "containerSecurityContext.runAsUser=0"

Step 4: Verify the installation

The daemonset's pod should show up and running almost immediately:

$ kubectl get all
NAME                         READY   STATUS    RESTARTS   AGE
pod/my-kured-chart-z7n7r   1/1     Running   0          52s

NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
service/kubernetes   ClusterIP   10.43.0.1    <none>        443/TCP   63s

NAME                              DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/my-kured-chart   1         1         1       1            1           kubernetes.io/os=linux   52s