Proxmox 8.2.4 Setup with 3 Nodes Cluster

[tls]

Hello Team

I am testing Proxmox 8.2.4 Setup with 3 Nodes Cluster
In India:
Node 1 BLR-ESI.local : IP 192.168.10.10
Node 2 MAA-ESI.local : IP 192.168.10.11
Node 3 DXB-ESK.local : IP 10.80.10.10

for creating a cluster. should be IP and Subnet same?
In my case Node 1 and Node 2 use 192.168.X.X and Node 3 use 10.80.XX.XX?

Can you share me the best practice links of necessary setups to be followed for Cluster and HA like video or article

 

[sw-omit]

Technically it would be possible, at least to create it, but if it is/will be stable will be a different question.

I would suggest to read through the cluster-manager documentation [1], especially the requirements.
The short of it is though:
Low latency and a stable, un-interupted connection is a must, highly preferably even on it's own seperate port/network, if you are on different networks, you'll always need some other thing (router or similar) to translate between the networks, adding (possible) delay and possible points of failure

Requirements​

• All nodes must be able to connect to each other via UDP ports 5405-5412 for corosync to work.
• Date and time must be synchronized.
• An SSH tunnel on TCP port 22 between nodes is required.
• If you are interested in High Availability, you need to have at least three nodes for reliable quorum. All nodes should have the same version.
• We recommend a dedicated NIC for the cluster traffic, especially if you use shared storage.
• The root password of a cluster node is required for adding nodes.
• Online migration of virtual machines is only supported when nodes have CPUs from the same vendor. It might work otherwise, but this is never guaranteed.

Network Requirements​

The Proxmox VE cluster stack requires a reliable network with latencies under 5 milliseconds (LAN performance) between all nodes to operate stably. While on setups with a small node count a network with higher latencies may work, this is not guaranteed and gets rather unlikely with more than three nodes and latencies above around 10 ms.
The network should not be used heavily by other members, as while corosync does not uses much bandwidth it is sensitive to latency jitters; ideally corosync runs on its own physically separated network. Especially do not use a shared network for corosync and storage (except as a potential low-priority fallback in a redundant configuration).
Before setting up a cluster, it is good practice to check if the network is fit for that purpose. To ensure that the nodes can connect to each other on the cluster network, you can test the connectivity between them with the ping tool.
If the Proxmox VE firewall is enabled, ACCEPT rules for corosync will automatically be generated - no manual action is required.

[1] https://pve.proxmox.com/wiki/Cluster_Manager