content/en/docs/next/networking/vm-external-vlan.md and the v1.6 copy both state that the vm-instance chart has no networkData and wires cloud-init through userData only. cozystack/cozystack#4306 changes that for guests with an ubuntu or debian instance profile: the chart then supplies its own cloud-init network-data, asking every en* and eth* interface for DHCP and accepting the DNS search domains offered over DHCP.
Two paragraphs on each page go stale when that PR lands. The first is in Step 3 — Attach the VM and assign a static address, which explains the userData recipe by the chart not supporting networkData; the reason changes, the recipe does not. The second is the No networkData bullet under Gotchas, which becomes the opposite of what the chart does — for those two profiles there now is a chart-supplied networkData, and no value replaces it. It does not conflict with the recipe, because netplan merges /etc/netplan/*.yaml and a higher-numbered file wins, but a static address still has to come from userData.
The equivalent paragraphs in this repository's own docs/vm-external-vlan.md are updated in that PR, so the wording can be taken from there once it merges. Filing this rather than a PR because the pages are per-version and the change should not land here before it lands upstream.
content/en/docs/next/networking/vm-external-vlan.mdand thev1.6copy both state that thevm-instancechart has nonetworkDataand wires cloud-init throughuserDataonly. cozystack/cozystack#4306 changes that for guests with anubuntuordebianinstance profile: the chart then supplies its own cloud-init network-data, asking everyen*andeth*interface for DHCP and accepting the DNS search domains offered over DHCP.Two paragraphs on each page go stale when that PR lands. The first is in Step 3 — Attach the VM and assign a static address, which explains the
userDatarecipe by the chart not supportingnetworkData; the reason changes, the recipe does not. The second is the NonetworkDatabullet under Gotchas, which becomes the opposite of what the chart does — for those two profiles there now is a chart-suppliednetworkData, and no value replaces it. It does not conflict with the recipe, because netplan merges/etc/netplan/*.yamland a higher-numbered file wins, but a static address still has to come fromuserData.The equivalent paragraphs in this repository's own
docs/vm-external-vlan.mdare updated in that PR, so the wording can be taken from there once it merges. Filing this rather than a PR because the pages are per-version and the change should not land here before it lands upstream.