Misleading documentation regarding ConfigMap/Secret volumes with VirtualMachinePools

[ravenix]

What happened:
Documentation states there would be two flags named "AppendPostfixToSecretReferences and AppendPostfixToConfigMapReferences" which would control adding a suffix to mounted configuration, such that virtual machines in the VMPool would be able to receive individual configuration. Actually, there are no such flags in the VMPool Spec, see also: https://github.com/kubevirt/api/blob/main/pool/v1alpha1/types.go

In the original design proposal of the VMPool resource such flag was acknowledged, but actually it was never implemented, nevertheless it found its way into the documentation.

What you expected to happen:
I expected to find a possibility to load individually rendered cloud-config into my VMPool VMs.

How to reproduce it (as minimally and precisely as possible):
There you go: https://kubevirt.io/user-guide/user_workloads/pool/#using-unique-cloudinit-and-configmap-volumes-with-virtualmachinepools

Additional context:
Those flags are not really optional; VMPool is more or less useless without it, because there is no sane way to load individual configuration in the according VMs otherwise. I spent half the day trying to solve this, but even the Hook system does not provide a solution here, because PreCloudInitIso is triggered before OnDefineDomain, so e.g. you can't really map your network devices to the actually assigned devices in certain configurations.

Environment:

• KubeVirt version (use virtctl version): all - since the beginning of the VMPool docs in March 2023
• Kubernetes version (use kubectl version): N/A
• VM or VMI specifications: N/A
• Cloud provider or hardware configuration: N/A
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Install tools: N/A
• Others: N/A

[aburdenthehand]

/cc @0xFelix Is this something you can help with?