Hello,
I am attempting to generate VM instances with predictable interface names using the name property for a bridged interface, however, this seems to have no affect on the instance at all as the interfaces still come up with the kernel generated enp#s0 identifiers.
Ideally I’d like to get DHCP on both interfaces which I am able to achieve by matching all if names as part of my cloud init and marking them DHCP, this, however, results in routing issues due to the multiple default gateways. If I am able to predict interface names then I can use dhcp4-overrides as part of my cloud-init to ignore one of the default gateways. Please let me know if my thinking is off here, I’m a recent VMware convert just getting started.
Here is my current interface configs, it’s not much and there are no issues that I can find in any sort of log, any help would be greatly appreciated, thanks!
devices:
clstr:
name: clstr
nictype: bridged
parent: cluster-net
type: nic
internet:
name: internet
nictype: bridged
parent: brInt
type: nic