Create virtual IP in VyOS for Silver Flame cluster #21

New Issue

Jafner · 2024-10-27T21:36:00-07:00

Jafner commented

2024-10-27 21:36:00 -07:00

Because our lab shares a public IP address with the rest of my home, we need to selectively forward traffic to our services. Thus far, we've accomplished that by port-forwarding service ports like HTTP/s (:80/:443) directly to the local IP address of our server.

As part of our migration to a highly-available cluster, we'll need to distribute traffic across all physical nodes.

Initial plan for this is to create a load-balancer to route TCP traffic to each of our nodes with round-robin.

Because our lab shares a public IP address with the rest of my home, we need to selectively forward traffic to our services. Thus far, we've accomplished that by port-forwarding service ports like HTTP/s (:80/:443) directly to the local IP address of our server. As part of our migration to a highly-available cluster, we'll need to distribute traffic across all physical nodes. Initial plan for this is to create a [load-balancer](https://docs.vyos.io/en/latest/configuration/loadbalancing/haproxy.html) to route TCP traffic to each of our nodes with round-robin.

Jafner commented

2024-10-28 00:18:38 -07:00

After digging deeper into the featureset provided by VyOS' "load-balancer" (actually just HAProxy), I think we may be able to implement a more powerful solution. But this will require deeper thought.

After digging deeper into the featureset provided by VyOS' "load-balancer" (actually just [HAProxy](https://www.haproxy.org/)), I think we may be able to implement a more powerful solution. But this will require deeper thought.

Jafner commented

2024-10-28 00:31:36 -07:00

To consider:

Can we eliminate NAT-based port-forwarding via reverse proxy?
Can we use the reverse proxy at level 7 without terminating TLS? (Transparent)

To consider: - Can we eliminate NAT-based port-forwarding via reverse proxy? - Can we use the reverse proxy at level 7 *without* terminating TLS? (Transparent)

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Jafner/Jafner.net#21