Installing the chart

Prerequisites

• Kubernetes 1.25+ (recommended 1.30+)
• Helm 3.19+

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-nginx-ingress oci://dhi.io/nginx-ingress-chart --version <version> \
  --set "controller.serviceAccount.imagePullSecretsName=helm-pull-secret" \

Note: As you might have noticed, upstream sets image pull secret slightly different to most charts.

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.

Note that this chart does not feature the NGINX Plus version and hence app protection with F5 WAF should not be enabled.

Step 4: Verify the installation

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

$ kubectl get all
NAME                                                       READY   STATUS    RESTARTS   AGE
pod/my-nginx-ingress-controller-846444b6fb-lgdpd           1/1     Running   0          30s

NAME                                          TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
service/kubernetes                            ClusterIP      10.43.0.1      <none>        443/TCP                      50s
service/my-nginx-ingress-controller           LoadBalancer   10.43.112.23   172.17.0.5    80:31935/TCP,443:31418/TCP   30s

NAME                                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/my-nginx-ingress-controller           1/1     1            1           30s

NAME                                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/my-nginx-ingress-controller-846444b6fb           1         1         1       30s

Note: