I might not deserve to say this, but I really wish Proxmox GmbH maintained an “official” terraform provider instead of relying on the community completely for it, à la Vates (XCP-ng). To be fair, it was the same with VMWare, so I’m not putting the blame on them.
For example, neither one out of the two well known Terraform providers (Telemate and bpg) support the newer SDN capabilities. Now, of course, it’s new so I completely understand that it would take time to write code for said functionality. Especially when it’s a community effort. It’s just that if Proxmox handled it directly I feel like the community would be able to better support them by supplementing features on top of a base that they create instead of going from scratch.
I believe Proxmox has said that Terraform is not their priority, and I understand. It’s a bad economy and companies are looking to downsize anyway. With that said, I hope I do get to see this someday.
Speaking of which, which IaC tool do you use for your Proxmox install/cluster?
I started writing a Terraform provider for Proxmox a while ago.
Unfortunately, the API is a massive mess and the documentation is not very helpful either. It was a nightmare and I eventually gave up.
even most cloud hosts beyond the big 3 + Digital Ocean don’t have an official terraform provider or ansible module it’s pretty ass.
A lot of them do actually. Most mid-tier cloud providers (Linode, Digital Ocean, Vultr) and less expensive providers (IONOS, for example) do have official terraform providers. Smaller providers like Racknerd don’t but that is somewhat understandable.
Incidentally, Porkbun is a known DNS provider which doesn’t have terraform support (which is why I’m evaluating Cloudflare in the first place for a domain).
XCP-ng has an official terraform provider, whilst ESXi and Proxmox don’t. The unfortunate part is that there isn’t even a provider for KVM, which really sucks.
XCP-ng has an official terraform provider, whilst ESXi and Proxmox don’t. The unfortunate part is that there isn’t even a provider for KVM, which really sucks.
Use LXD/Incus instead, there’s a provider for it.
I’m using the bpg provider - but I share your pain. Both providers had things that don’t work so I went with the one that supported my use-case better. But it’s not ideal.
I would love an official provider.
Ye
Well Proxmox doesn’t have it… however LXD/Incus has one. Maybe you should try it as a replacement for Proxmox? I mean it’s new, new generation software, can be installed in a clean Debian 12 setup from the repositories and does both containers and VMs.
Thanks, it’s very new and I’d like to give it some time to mature. With that said, I’m happy to see a SUSE developer take it on.
It also has some great capabilities and let’s me handle my storage and hardware whilst providing me paradigms akin to the Cloud a la Openstack (to an extent). It seems great, thanks for mentioning it.
Very new? The thing has been around since 2018. Anyways I know for a fact that a few cloud providers and some enterprise types are using it to power their infrastructure.
Could you tell me which cloud providers are using Incus?
It’s a bit hard to search info about it with the name. But it’s a fantastic project
It’s a bit hard to search info about it with the name. But it’s a fantastic project
Searching for LXD usually returns more useful information… Incus is just a fork as you know.
