I use a Debian-based custom application that is also available in the Azure Marketplace. I deploy two nodes, it works without any problems.
Within this application there is the possibility of building a cluster. The cluster setup works, but the DB-IP cannot be reached after the setup. I strongly suspect that this is a configuration error on my part.
The cluster works without problems in OnPrem environments.
The construction is very simple
2 nodes + Virtual Database IP in the same subnet. Actually, only a free IP from the subnet has to be used for the Virtual Database IP.
So I created a network group (Vnet) in Azure, there are the two nodes and there are free IPs in this subnet.
Unfortunately, as written, the IP cannot be reached after it has been set up. I have already tried to outsource the IP to a separate interface - without success.
The virtual database IP is linked to the primary node during cluster setup, but must be accessible from both nodes.
Unfortunately I haven't found a way to create an "empty" internal IP in Azure - only public IPs can be created.
Does somebody has any idea?
Thanks in advance for your help