Tracked topic
Instead of dynamically building VM images on every provision, I used existing Proxmox VM templates. My templates already had cloud-init enabled, SSH access configured, and base OS packages installed. This gave me: Faster VM provisioning — no image builds in the critical path Better control over OS hardening — managed outside the Kubernetes workflow Easier debugging — when something goes wrong, the VM layer is a known quantity
K3s on On-Prem Infrastructures the GitOps Way: Writing a Custom k0rdent Template from Scratch… Step 1: Infrastructure Provider BYOT k0rdent doesn’t ship with a native Proxmox provider, so we built one. We created a custom Helm chart that acts as an Infrastructure Provider for Proxmox. …
… Rather than reaching for imperative vSphere tooling, we use VirtRigaud , a Kubernetes operator that provides declarative VM management across multiple hypervisors vSphere, Libvirt/KVM, and Proxmox through a unified CRD API. …