This is a Helm chart for deploying the Pi-hole workload to a Kubernetes cluster.
IMPORTANT:
- This chart publishes the DNS service of Pi-hole on port 53 TCP and UDP on an IP address provided by an external load balancer service! Please check your Kubernetes distribution or Cloud provider for the available options.
- The configuration data for the Pi-hole service is stored in a separate persistent volume so that it survives re-deployments.
Provide a persistent volume for this chart in your cluster. Check Pi-hole Volume Chart for an example if you need help.
Check the file values.yaml.
Consider this file being read-only and put your customizations into a file named custom.yaml instead, so that you
don't get merge conflicts when you pull the changes from this repository.
The files are merged before deployment so that custom.yaml gains priority over values.yaml.
make [up]
make down