terraform-provider-proxmox VS k3d

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

K3D: is a lightweight distribution of Kubernetes designed for resource-constrained environments. It is an excellent option for running Kubernetes on virtual machines or cloud servers.

k3d is a lightweight wrapper that makes running Kubernetes (specifically, the lightweight k3s distribution) in Docker straightforward and efficient. It's designed to provide developers with a quick and easy way to test Kubernetes without the overhead of setting up a full cluster.

If you customer prefers to run the standard docker engine you could use k3d

You don’t need to run Rancher from a Kubernetes cluster, the rancher/rancher image works fine with Docker (it uses k3d, aka « k3s in docker » : https://k3d.io/).

K3d and Skaffold for local development

If you are a developer and want to learn how to deploy applications to a cluster, getting a cluster up an running can be a daunting task in it's own rights. There are many ways to do it: spinning up local virtual machines and configuring from scratch or using tools like minikube, etc. You may not care for the pain of setting up and configuring a cluster, and if that is you, then the quickest way that I have found is using k3d.