Attach Public IP to VM

As a Cozy user, I would like to attach a Public IP directly to VM resources

Matthieu ROBIN (@matthieu-robin)

Hi Matthieu ROBIN (@matthieu-robin). We were considering various implementations.

We have a few options here:

Publish the VM as a Kubernetes service; this case is already working.
Specify a public IP for the VM using Kube-OVN and attach it to the default interface. Not sure if it will work fine, but it might, with the limitation of only one IP per virtual machine.
Use Multus to add a secondary interface to the VMs; this might be a solution, with the limitation that these secondary interfaces will be used only for assigning public IPs to VMs, but not for managed services. We also can't reuse this approach for the normal Pods because it bypasses the Kubernetes networking stack.

We have a pool of public IP ( the one used by Ingress), it should be great if this one is used.
And for us, a second network interface should be the best way to manage security and rules.
Thanks

Isn't the public IP basically attached to the VM as s service (type=LoadBalancer)?,
e.g. 172.23.168.26 in the following case:

% k get service vm-instance-vmi3
NAME               TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)   AGE
vm-instance-vmi3   LoadBalancer   10.96.29.224   172.23.168.26   22/TCP    44h

So considering you have address pool, you declare it as an ipaddresspools.metallb.io and that's it.

done in #615

[linstor] Build linstor-server with custom patches (#1726)

Navigation Menu

Repository navigation

Attach Public IP to VM #474

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Attach Public IP to VM #474

Description

Activity

kvaps commented on Nov 12, 2024

matthieu-robin commented on Nov 12, 2024

c42-konstantin commented on Jan 23, 2025

kvaps commented on Mar 25, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions