blocky VS terraform-provider-proxmox

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.

Mildly relevant - the Telmate Terraform provider for Proxmox [1], which now stopped working with latest Proxmox version due to seemingly being abandoned, was initially mostly developed by an engineer employed by a company of the same name. They've since rebranded [2].

I've used that provider for a while, and only recently started looking into the specifics. The repo is effectively owned by a company profiting off of incarcerated persons in the US. Pretty wild.

Mostly writing this since I've spent the last few days migrating my Terraform setup to a different, supported provider [3].

[1] https://github.com/Telmate/terraform-provider-proxmox

That's the right answer! Backup all the data that you value, for the rest use the automation tools. Use Ansible to configure the servers and Terraform to provision Proxmox, terraform-provider-proxmox.

Nice guide! It's really a shame that https://github.com/Telmate/terraform-provider-proxmox/issues/600 still hasn't been fixed, otherwise Telmate would be pretty solid. It works pretty well if you don't tinker with multiple applies, though.

I have looked into the Terraform Proxmox provider: https://github.com/Telmate/terraform-provider-proxmox but I don't see anything for creating the disk outside the VM. I'm also not sure how to set any ID for a disk and use that to mount in /etc/fstab. So I'm wondering if my idea even is possible?

So the principle I'm working with is that each of my machines are partially dedicated to running workloads in k3s, about 50-90% each. I use proxmox vms created with https://github.com/Telmate/terraform-provider-proxmox for upgrades and for experimenting with cluster config.

I faced this same error in Ansible instead of Terraform, but it means that one of the parameters given is not accepted. If you are using the Telmate provider, try adding these options to find out which parameter is causing the error. For my case, it was a typo in my IP address string.

Hello guys, For days I'm playing with Telmate/Proxmox Terraform provider/plugin and its very poor experience.

Work stuff. We heavily rely upon terraform-provider-proxmox and by extension proxmox-api-go. Both of those projects need serious love.

I've looked at this in the past and this provider seems to be the one to go with https://github.com/Telmate/terraform-provider-proxmox