You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @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
As a Cozy user, I would like to attach a Public IP directly to VM resources
The text was updated successfully, but these errors were encountered: