Future Plans for K8s Multi-Network IPAM Support

[infinitydon]

Hi Spiderpool team,

I'm interested in learning about Spiderpool's roadmap regarding Kubernetes Multi-Network (KEP-3177) from an IPAM perspective. As Spiderpool is focused on IP address management, I'm curious about how you envision handling IPAM requirements in the upcoming native multi-network environment.

Refs:

https://docs.google.com/document/d/1pe_0aOsI35BEsQJ-FhFH9Z_pWQcU2uqwAnOx2NIx6OY/edit?tab=t.0#heading=h.fo1yo94x96wg

https://github.com/mskrocki/enhancements/blob/mn-req/keps/sig-network/3698-multi-network/README.md

https://github.com/LionelJouin/network-dra

Currently, Spiderpool works well with Multus for managing IP allocations across multiple networks. However, as Kubernetes moves towards native multi-network support, there might be new considerations for IPAM solutions:

• Managing IP pools across multiple network interfaces within the native K8s multi-network framework
• Handling IP allocation strategies when pods have multiple network attachments
• Coordinating with the native multi-network controller for IP assignments
• Supporting different IP management policies per network interface

Given these potential changes to the networking landscape, I have a few questions:

1. Is Spiderpool planning to adapt its IPAM capabilities to support native K8s Multi-Network?
2. How do you envision the transition of IPAM functionality from the current Multus-based approach to the native multi-network implementation?
3. Are there specific IPAM features or capabilities you think would be important to add or modify to better support native multi-network scenarios?

I believe this discussion could help the community understand how IPAM solutions like Spiderpool will evolve alongside Kubernetes networking capabilities. Looking forward to hearing your thoughts!

Thanks