Does DraNet support IPAM (auto-assign IPs) for attached interfaces?

[bhatnitish]

I’m using DraNet to attach a NIC to a Pod and can successfully set interface attributes (name/mtu/offloads) and static IPs via parameters.interface.addresses. For larger deployments I’d like the IPs to be allocated automatically (IPAM) instead of hardcoding them per workload. Is that possible today? I looked at the docs/examples and didn’t find anything obvious—so I’m checking whether this is already supported (and I missed it), on the roadmap, or out of scope.

[aojea]

hi @bhatnitish, thanks for the feedback.

The IPAM topic is challenging, and we want to understand better the use cases out there to try to model it right.
We have very basic support, mostly building blocks:

• The automated allocation today relies on the attached interface to be attached to a network with DHCP.
• The DRANET internal API already allows user to specify an IP address, that makes it possible to create some automation that sets this IP

Please help us understand better how are you expecting to use it, I'm specially interested on how to model the relation between IPAM, Nodes, and Interfaces, since this will require the IPAM to be able to have visibility on the external networks where the attached interfaces are connected