dhi.io/prometheus-adapter-chart
Helm chart for Prometheus Adapter (custom.metrics.k8s.io API) using Docker Hardened Images.
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:
dhi.io/<repository>:<tag><your-namespace>/dhi-<repository>:<tag>For more details about customizing the chart to reference other images, see the documentation.
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
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>
To install the chart, use helm install. Optionally, you can also use the --dry-run flag to test the installation
without actually installing anything. 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.
Bear in mind that when using the DHI Prometheus Helm chart with its default values, the Kubernetes Service exposes port 80 inside the cluster instead of Prometheus' default port (9090).
helm install my-prometheus-adapter oci://dhi.io/prometheus-adapter-chart --version <version> \
--set "image.pullSecrets[0].name=helm-pull-secret" \
--set prometheus.url=http://prometheus.monitoring.svc \
--set prometheus.port=<prometheus_port>
The deployment's pod should show up and running almost immediately:
$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/my-prometheus-adapter-prometheus-adapter-chart-xxx 1/1 Running 0 30s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 1m
service/my-prometheus-adapter-prometheus-adapter-chart ClusterIP 10.43.x.x <none> 443/TCP 30s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/my-prometheus-adapter-prometheus-adapter-chart 1/1 1 1 30s