One set of templates, multiple clusters

Sep 11, 2025
23
11
3
johannes.truschnigg.info
Since our migration away from VCF and onto PVE, we've successfully remodeled template creation (both for containers using debootstrap and qemu VMs using hashicorp's packer) for the new environment, but are scratching our heads what's the most convenient approach to roll out out one set of templates (including VM template metadata) to all our independent clusters. Right now, we are deploying the resulting .tar.gz container rootfs as well as the generated qcow2 image to a universally available SMB share, but at least for VMs, that image's availability solves only part of the problem.

Does anyone on these forums have a similar problem - and maybe even a solution to it? :)
 
  • Like
Reactions: mpit
We can share the resulting disk image between clusters via shared storage, but that does not establish template machine definitions in these clusters where we'd like to be able to "clone" from - think Hardware settings, cloud-init parameters, general VM options, ...
 
Yes, you'd need to create a VM config manually across the clusters. Note that sharing configuration and disks across clusters is not something that is officially supported, or tested. It should work with immutable type of VM such as a Template, but you should still be careful about it.



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
What about cloning the template and then do a remote migration to the other clusters or are they network-wise not reachable?
For sure you then have completely independent templates but you can directly use it in the cluster without creating any VM config. Maybe some settings like cpu type, storage or interface need to be adjusted.