You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: