Recently I tried to get my head around cloud init, did get it to work but found a bigger question.
In my use case, I'm using jammy-server-cloudimg-amd64.img as base image due to kernel compatibility, and found I need to apply 2 custom yaml. One is setting different metric to multiple NICs, and install qemu-guest-agent so PVE can property shut it down.
They are relatively straight forward with cicustom: network= & vendor= custom yaml, well documented here https://pve.proxmox.com/wiki/Cloud-Init_Support
My challenge comes cloning or migrating the custom yaml files.
I found when I full clone a template, the new VM still reference original yaml rather than new copy.
I also found when migration between PVE nodes, the yaml stays on original node rather than being copied along.
While both can be easily managed via SSH commands, but that kinda defeats the purpose of using cloud-init to simplify/automate VM creation.
So is this just how it is with PVE, or am I missing something?
In my use case, I'm using jammy-server-cloudimg-amd64.img as base image due to kernel compatibility, and found I need to apply 2 custom yaml. One is setting different metric to multiple NICs, and install qemu-guest-agent so PVE can property shut it down.
They are relatively straight forward with cicustom: network= & vendor= custom yaml, well documented here https://pve.proxmox.com/wiki/Cloud-Init_Support
My challenge comes cloning or migrating the custom yaml files.
I found when I full clone a template, the new VM still reference original yaml rather than new copy.
I also found when migration between PVE nodes, the yaml stays on original node rather than being copied along.
While both can be easily managed via SSH commands, but that kinda defeats the purpose of using cloud-init to simplify/automate VM creation.
So is this just how it is with PVE, or am I missing something?