A little confused about OVN load-balancing and Proxy?

Greetings team,

So I have an instance in my ovn network and I would like to be able to reach it from my lan network. I was reading and thinking about the best way to do this and I decided to try it via load-balancing. I am unsure if what I am doing is correct, but I created a load-balancer and add one of my linstor test nodes to the load-balancer and I would like to be able to reach the gui (which is installed and on port 8080).

I can’t reach it via the network volatile ipv4 address that its on, did I miss something?

Here is my ovn network

root@supermicro:/home/mihai# incus network list
+-----------------+------+---------+----------------+---------------------------+------------------+---------+---------+
|      NAME       | TYPE | MANAGED |      IPV4      |           IPV6            |   DESCRIPTION    | USED BY |  STATE  |
+-----------------+------+---------+----------------+---------------------------+------------------+---------+---------+
| linstor-testing | ovn  | YES     | 10.18.191.1/24 | fd42:4360:9cd5:ae3f::1/64 | linstor testing  | 0       | CREATED |
+-----------------+------+---------+----------------+---------------------------+------------------+---------+---------+
root@supermicro:/home/mihai# incus network show linstor-testing
config:
  bridge.mtu: "1500"
  ipv4.address: 10.18.191.1/24
  ipv4.nat: "true"
  ipv6.address: fd42:4360:9cd5:ae3f::1/64
  ipv6.nat: "true"
  network: UPLINK-admin_labs
  volatile.network.ipv4.address: 10.200.10.2
description: 'linstor testing '
name: linstor-testing
type: ovn
used_by: []
managed: true
status: Created
locations:
- r620
- r720-3
- supermicro
- r720-2
project: admin-labs

Here is my UPLINK

root@supermicro:/home/mihai# incus project switch default
root@supermicro:/home/mihai# incus network show UPLINK-admin_labs
config:
  dns.nameservers: 1.1.1.1
  ipv4.gateway: 10.200.10.1/24
  ipv4.ovn.ranges: 10.200.10.2-10.200.10.254
  volatile.last_state.created: "false"
description: ""
name: UPLINK-admin_labs
type: physical
used_by:
- /1.0/networks/linstor-testing?project=admin-labs
managed: true
status: Created
locations:
- supermicro
- r720-2
- r620
- r720-3
project: default

Here is my load-balancer

root@supermicro:/home/mihai# incus network load-balancer show linstor-testing 10.200.10.2
description: ""
config: {}
backends:
- name: linstor-gui
  description: ""
  target_port: "8080"
  target_address: 10.18.191.2
ports:
- description: ""
  protocol: tcp
  listen_port: "8080"
  target_backend:
  - linstor-gui
listen_address: 10.200.10.2
location: ""
root@supermicro:/home/mihai# incus network load-balancer list linstor-testing
+----------------+-------------+-------+----------+
| LISTEN ADDRESS | DESCRIPTION | PORTS | LOCATION |
+----------------+-------------+-------+----------+
| 10.200.10.2    |             | 1     |          |
+----------------+-------------+-------+----------+

And my instance
root@supermicro:/home/mihai# incus ls

+----------+---------+----------------------+-------------------------------------------------+-----------------+-----------+------------+
|   NAME   |  STATE  |         IPV4         |                      IPV6                       |      TYPE       | SNAPSHOTS |  LOCATION  |
+----------+---------+----------------------+-------------------------------------------------+-----------------+-----------+------------+
| linstor1 | RUNNING | 10.18.191.2 (enp5s0) | fd42:4360:9cd5:ae3f:216:3eff:fe1f:30b0 (enp5s0) | VIRTUAL-MACHINE | 0         | supermicro |
+----------+---------+----------------------+-------------------------------------------------+-----------------+-----------+------------+

Do you get the same result if you give it an address other than the one already used by the logical router of your network?

Say give 10.200.10.3 to the load-balancer instead?

I just figured it out @stgraber , I had the wrong port. Sorry about that !

Oh, that’d explain it :slight_smile: