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?

  • @MigratingtoLemmy@lemmy.worldOP
    link
    fedilink
    English
    210 months ago

    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.

    • @TCB13@lemmy.world
      link
      fedilink
      English
      -510 months ago

      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.