charts/charts/blocky

DNS proxy as ad-blocker for local network

This is an opinionated helm chart for blocky

The default values and container images used in this chart will allow for running in a multi-arch cluster (amd64, arm, arm64)

TL;DR

helm repo add k8s-at-home https://k8s-at-home.com/charts/
helm install k8s-at-home/blocky

Installing the Chart

To install the chart with the release name my-release:

helm install --name blocky k8s-at-home/blocky

Uninstalling the Chart

To uninstall/delete the blocky deployment:

helm delete blocky --purge

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

Read through the values.yaml file. It has several commented out suggested values.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

helm install --name blocky \
  --set timeZone="America/New York" \
    k8s-at-home/blocky

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

helm install --name blocky -f values.yaml k8s-at-home/blocky

Upgrading an existing Release to a new major version

A major chart version change (like 2.2.2 -> 3.0.0) indicates that there is an incompatible breaking change needing manual actions.

Upgrading from 2.x.x to 3.x.x

Due to the renaming of the service port, an upgrade-in-place will not work. The following are possible approaches to solve this:

Helm force upgrade

helm upgrade --force

Delete the existing blocky service prior to upgrading

kubectl delete svc/blocky

Remove the existing blocky chart first

This is the 'easiest' approach, but will incur downtime which can be problematic if you rely on blocky for DNS