Afterburn supports Proxmox VE but is excluded from configuring network before Ignition

[alliek-mti]

Description

The afterburn-network-kargs.service (Flatcar / bootengine) kicks off the coreos-metadata program responsible for making the network configuration available before Ignition starts trying to download files. But a set of "ConditionKernelCommandLine" settings restricts this functionality to VMWare despite it apparently being available under Proxmox VE.

Impact

Can't download files from Ignition, so things like sysexts have to be added manually afterwards.

Environment and steps to reproduce

Using the instructions here https://www.flatcar.org/docs/latest/installing/community-platforms/proxmoxve/ as a template.

Assign a static IP and gateway as described here: https://pve.proxmox.com/wiki/Cloud-Init_Support

Use an Ignition file that invokes storage.files.contents.source with a URL.

Ignition will go into a loop failing to even look up the server via DNS.

Expected behavior

Static IP, gateway, and DNS should be configured before Ignition reaches the "files" stage when the data is available to do so.

Additional information

After a bit of a source dive through dracut and afterburn, I believe that the coreos-metadata tool already has everything it needs to fetch the networking configuration provided by Proxmox VE. It just isn't being given a chance.

If these lines were present:

ConditionKernelCommandLine=|coreos.oem.id=proxmoxve
ConditionKernelCommandLine=|flatcar.oem.id=proxmoxve

...I believe this would succeed.

Note that testing this requires use of a static IP. The example provided on flatcar.org uses DHCP, which may have inadvertently masked the issue as it appears DHCP is configured by zz-default.network.