search

FyraLabs / chisel-operator

Kubernetes Operator for Chisel
https://chisel.fyralabs.com
GNU General Public License v3.0
80 stars 8 forks source link

Multiple exit nodes per service #9

Open ammmze opened 8 months ago

ammmze commented 8 months ago

This looks like a great project! I'll be exploring this in the next few days. One thing I see missing that I'd like to see supported is having multiple exit nodes per service.

I've got a couple of cheap VPS machines that I have setup under a single CNAME (so basically load balancing at the DNS level) and I'd like to have both of them setup as exit nodes for the same nginx ingress service.

For the manually provisioned nodes, I think this is more/less just a matter of making the exit node name label a comma list of exit nodes, then when processing that label we split the label and iterate over individual values.

We may also need to have some consideration around updating the load balancer ip addresses in the service to ensure they don't override the other.

korewaChino commented 7 months ago

Honestly I don't even know if Chisel actually lets you run multiple reverse-proxy clients to one server (with different ports ofc).

But if you want a HTTP LB, I recommend just running the reverse proxy on the cluster itself.

I might work on this soon, just hold on a bit :3

korewaChino commented 1 month ago

This should hopefully be fixed as of https://github.com/FyraLabs/chisel-operator/commit/d50d5e0845cabff6e3307596f4770f81087feb8b, needs testing

korewaChino commented 1 month ago

Oops, got confused with #92