kind VS terraform-provider-proxmox

To get started, you'll need to install clusteradm and kubectl and start up three Kubernetes clusters. To simplify cluster administration, this article starts up three kind clusters with the following names and purposes:

Kind: is a tool for running local Kubernetes clusters using Docker container "nodes." It was primarily designed for testing Kubernetes itself but can also be used for local development or continuous integration.

Fortunately, just as projects like kind and Minikube enable developers to spin up a local Kubernetes environment in no time, CRC, also known as OpenShift Local and a recursive acronym for "CRC - Runs Containers", offers developers a local OpenShift environment by means of a pre-configured VM similar to how Minikube works under the hood.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Features compared to https://kind.sigs.k8s.io/

Kind allows you to run a Kubernetes cluster inside Docker. This is incredibly useful for developing Helm charts, Operators, or even just testing out different k8s features in a safe way.

Check out KinD

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.

We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.

yes I know there is lens, but it does not allow me to see logs of multiple pods at same time and what is even more important it is not friendly for ephemeral clusters - in my case with help of kind I am recreating whole cluster each time from scratch

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