IP Conflict Concern in Cluster API Provider for Proxmox.

[PixelWhisper3r]

Description

While using Cluster API Provider (CAPI) with Proxmox, have to manually enter a static IP for the control plane endpoint and the virtual IP (VIP). This raises a concern about potential IP conflicts, especially in dynamic or large-scale environments where IP management is complex.

I wanted to ask if there is any mechanism in place (or planned) to handle IP allocation dynamically to avoid conflicts, or if there are best practices recommended for managing this manually.

Expected Behavior

• Ideally, there should be a way to manage IP assignment dynamically to prevent conflicts.
• If manual IP assignment is the only way, best practices or guidance would be helpful.

Actual Behavior

• Users need to manually assign a static IP, which may lead to IP conflicts if not managed properly.

Steps to Reproduce

1. Set up Cluster API Provider (CAPI) with Proxmox.
2. Assign a static IP for the control plane endpoint and virtual IP (VIP).
3. Deploy the cluster.
4. If another device already has the same IP, a conflict may arise.

Additional Notes

I apologize if this is a silly issue—I’m completely new to CAPI and Proxmox. I just wanted to clarify how to handle this situation properly.

Lastly, thank you for creating this amazing infrastructure provider! I really appreciate the effort that has gone into making it available.

[mcbenjemaa]

We have plans to support DHCP #29, but that would require you to set up a DHCP server yourself.
However, we also might introduce new IPAM providers in future.

[PixelWhisper3r]

Thank you for the response.

I just wanted to clarify—if I understand correctly, the DHCP support would primarily handle machine IPs. However, my concern is specifically about the virtual IP (VIP) and the control plane endpoint.

Is there anything planned for managing those dynamically as well? Or would manual IP assignment remain the only option for them?