Feature: Implement Dynamic IPAM for the Slice Overlay Network

[gourishkb]

🔖 Feature description

In the current KubeSlice design, IP address management (IPAM) for slice overlay networks is static and inefficient. A predefined CIDR block (e.g., 10.1.0.0/16) is divided into a fixed number of subnets regardless of how many clusters participate in the slice, leading to significant IP space wastage.

🎤 Pitch

This issue aims to implement a dynamic IPAM system that allocates IP subnets to clusters on demand and reclaims unused ranges when clusters leave the slice. It will ensure efficient address utilization, synchronization across clusters, and integration with the KubeSlice control plane.

✌️ Solution

• A dynamic IPAM allocator integrated with the KubeSlice controller or sidecar component.
• Support for on-demand IP allocation and subnet reclamation when clusters join or leave a slice.
• Conflict resolution and state synchronization across clusters using CRDs or distributed storage.
• Documentation on how the system works, configuration options, and edge case behaviour.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[Sukuna0007Abhi]

Hi @gourishkb I'm trying to contribute to this org, not only just for this Lfx part also for learning this repo and gain some exp but I see that there are not much good first issues are there, kindly could you suggest me some issues so I could start to work.Happy to contribute @gourishkb @priyank-upadhyay @narmidm @tamalsaha @richiesebastian

[Anxhul10]

better way to start would be theses issues: KubeSlice Roadmap