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?

14 points

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.

https://github.com/c10l/terraform-provider-proxmoxve

permalink
report
reply
2 points

Very unfortunate. I’m considering OpenStack as an alternative for its support but TBH it’s not what I want.

permalink
report
parent
reply
4 points

I might pick it back up some day but at the moment I have other projects going on at the moment.

I’m still using Proxmox myself but unfortunately it’s all fairly manually configured.

permalink
report
parent
reply
4 points

It’s just that when something breaks in Proxmox the remediation is completely manual and I hate that.

Thanks, I look forward to someone creating a provider which encompasses all of Proxmox.

permalink
report
parent
reply
1 point
*

If you’re willing to go the extra mile for OpenStack, I suggest you check out OKD and its virtualization operator. It’s much easier to install and maintain, too

permalink
report
parent
reply
1 point

Thanks I’ll take a look

permalink
report
parent
reply
6 points

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.

permalink
report
reply
1 point

This… bpg provider seems to check most boxes and I’ve had less quirks than Telmates. My biggest gripe with most / all of them is the lack of cluster support.

permalink
report
parent
reply
5 points

even most cloud hosts beyond the big 3 + Digital Ocean don’t have an official terraform provider or ansible module it’s pretty ass.

permalink
report
reply
2 points

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.

permalink
report
parent
reply
-5 points

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.

permalink
report
parent
reply
4 points
*

Yeah, I feel that. I’ve settled on telmate’s but there’s a few things I’ve had to implement as hacky post creation SSH edits on the config files, such as passing through the Intel GPU to my Jellyfin container.

permalink
report
reply
5 points

AFAIK bpg’s provider has significantly better feature-support than Telemate

permalink
report
parent
reply
2 points

Ah, I see. I’ll check it out!

permalink
report
parent
reply
2 points
*

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
ESXi VMWare virtual machine hypervisor
SSH Secure Shell for remote terminal access

[Thread #522 for this sub, first seen 17th Feb 2024, 20:45] [FAQ] [Full list] [Contact] [Source code]

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.9K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments