pihole-kubernetes VS blocky

I'm running 2 instances of pihole on my k8s(k0s) cluster. I was feeling like a slacker so I started using this helm chart here to deploy them instead of writing my own https://github.com/MoJo2600/pihole-kubernetes. The problem is, they use a Deployment and not a Stateful Set. This means if I can't raise the deployment count unless I stop using persistent storage.

The only thing I've really got is PiHole for k8s (https://github.com/MoJo2600/pihole-kubernetes/tree/master/charts/pihole).

I run multiple blocky instances in a kubernetes cluster. I don't know if it makes sense ... but I'm running kubernetes cluster at home, so making sense is relative ;p

The PI is running a DNS proxy (https://github.com/0xERR0R/blocky) and not much else at the moment.

I switched from pihole to https://github.com/0xERR0R/blocky for internal DNS, and I found it to be a lot easier to use compared to pihole. Setting up DNS entries was as easy as typing a single line in their config.yml, and restarting the service.

You could try using blocky instead of pihole. It's stateless and much more friendly to run.

Link to the Projects' GitHub pages: 1. https://github.com/0xERR0R/blocky [Blocky] 2. https://github.com/AdguardTeam/AdGuardHome [AdguardHome] 3. https://github.com/pi-hole/pi-hole [Pi-hole]

Any specific feature you need from pihole that Blocky doesn't have? Blocky is a much nicer tool for AdBlocking especially if deployed in k8s because it's stateless and configured via a single config file. Plus it's written in Go!

Still, to answer the question: https://github.com/0xERR0R/blocky

There is also blocky. I like it because it is light, declarative, stateless, can use redis as cache and has prometheus integration. This plays really nicely with my setup.