dhi.io/istio-ingress-chart
Istio Ingress Helm chart
Helm chart for deploying Istio gateways.
Installing the chart
Prerequisites
- Helm 3.6+
- Kubernetes cluster with Istio control plane already installed (
istio-baseandistio-discovery)
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 chart
Install the chart with a release name and namespace. The ingress gateway is typically installed in a dedicated namespace
(e.g. istio-ingress). Make sure istio-discovery is already running before installing this chart, as the ingress
gateway requires the Istio control plane to be available.
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 istio-ingress oci://dhi.io/istio-ingress-chart --version <version> \
-n istio-ingress --create-namespace \
--set "global.imagePullSecrets[0]=helm-pull-secret"
Replace <version> accordingly. If the chart is in your own registry or namespace, replace dhi.io with your own
registry and namespace. Replace helm-pull-secret with the name of the image pull secret you created in Step 2.
For more options and values, see the Istio installation documentation.
Step 4: Verify the installation
The ingress gateway deployment and pods should show up and be running in the istio-ingress namespace:
$ kubectl get all -n istio-ingress
NAME READY STATUS RESTARTS AGE
pod/istio-ingressgateway-77c76cc77c-d9tgz 1/1 Running 0 22s
pod/istiod-7bc598ff46-5l6q7 1/1 Running 0 31s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/istio-ingressgateway LoadBalancer 10.43.64.151 172.17.0.5 15021:30750/TCP,80:30675/TCP,443:32209/TCP 22s
service/istiod ClusterIP 10.43.184.62 <none> 15010/TCP,15012/TCP,443/TCP,15014/TCP 31s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/istio-ingressgateway 1/1 1 1 22s
deployment.apps/istiod 1/1 1 1 31s
NAME DESIRED CURRENT READY AGE
replicaset.apps/istio-ingressgateway-77c76cc77c 1 1 1 22s
replicaset.apps/istiod-7bc598ff46 1 1 1 31s
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
horizontalpodautoscaler.autoscaling/istio-ingressgateway Deployment/istio-ingressgateway cpu: <unknown>/80% 1 5 1 22s
horizontalpodautoscaler.autoscaling/istiod Deployment/istiod cpu: <unknown>/80% 1 5 1 31s
Uninstall
helm uninstall istio-ingress -n istio-ingress