Closed
Description
Please describe the solution you would like.
If a user supplies Cloud-Init userdata that exceeds 64KiB once it is gzipped and base64 encoded, the VM should have a condition added to it indicating the userdata is invalid due to size restrictions. The maximum size of any guestinfo value is 64KiB.
And because guestinfo values can be stored in the vmx file, the vmx file has a maximum size (by default) of 1MiB, although this is configurable via the property tools.setInfo.sizeLimit.
The condition added to a VM should also apply to the generated Cloud-Init metadata, both combined with the userdata or separately.
- If userdata exceeds 64KiB, error
- If metdata exceeds 64KiB, error
Is there anything else you would like to add?
NA
Please tell us about your environment.
| Value | How to Obtain | |
|---|---|---|
| Supervisor version | NA |
rpm -qa VMware-wcp on the vCenter appliance |
| Supervisor node image version | NA |
rpm -qa VMware-wcpovf on the vCenter appliance |
| Kubernetes version | NA |
kubectl version |
| VM Operator version | NA |
kubectl -n vmware-system-vmop get pods \
-ojsonpath='{range .items[*].spec.containers[*]}{.image}{"\n"}{end}' | \
sort -u | \
grep vmop | \
awk -F'/' '{print $3}' | \
awk -F: '{print $2}' |