Hetzner Proxmox Cluster and vswitch configuration

[Prime_T]

Hi all ,
Initial setup:
I have deployed a proxmox on a single node then turned it into a cluster by adding two nodes on dedicated servers on hetzner cloud .
In order to ensure communication between the nodes i configured a vswitch and added the 3 nodes. I have configure the ha manager and rules on few vm to test node failure.

Problem:
I want a private network to span all over the 3 nodes, so all resources can ommunicate with each other (1) and in case of node failure, auto migration would take place and the vm will still have a valid ip address and be able to connect to public internet (2).

Note: all resources should be able to connect to public internet despite where the vm resides
Obstacle: each vm has a gateway that changes from node to node and therefore after migration connectivity to public internet will be lost

 

[j.theisen]

Hi @Prime_T

thanks for posting on the forum!
I personally have a similar setup at Hetzner with two dedicated servers and a separate QDevice.

What kind of gateway are you using for your VMs to access the internet?

In my case i used a pfsense VM and gave it an interface in the VLAN zone of the VMs so that it can act as a default gateway.
The inter-node communication runs through the Hetzner vSwitch you already mentioned so the VMs can communicate with each other independent of the node they are on.

Is there something specific in your environment that prevents you from using a VLAN on Hetzners vSwitch?

Best regards
Jonas

 

[Prime_T]

Hi again
Thank you for your response @j.theisen.

I'm using 10.0.30.254/24 as gateway. i configured the other nodes no have the same gateway . But i don't want to leave a single point of failure because if i use one default gateway it can go down and i lose connection.
I'm already using a vSwitch to connect all servers and it's used for ceph and OSDs specifically. I have two other vSwitchs but i want to know how to span one network for the whole cluster (1), avoid the gateway problem and ensure connection to public internet (2) and ensure high-availability via ha-manager and migration process afterwards(3), since it's all related .