3 ms·
Got it, very helpful. We are looking at it to do dynamic routing from our system to the Internet and back. That means terminate the request on a client (server
by doh 8y ago
Got it, very helpful.
We are looking at it to do dynamic routing from our system to the Internet and back. That means terminate the request on a client (server), route it to an exit node where it's more appropriate (for instance to bypass GEO restriction) and then send the response back to the origin.
We are looking at some other alternatives, like envoy + istio + gloo, but skipper seems more contained and less container depended.
- rdli 8y agoDid you check out Ambassador by any chance?
- doh 8y agoI did. Its not that far from Gloo. I would like something that doesn’t require crazy amount of tooling and does require containers
- sszuecs 8y agoI would be happy to help in case you see performance or scaling issues with skipper. If you like join our Gopher slack channel #skipper in gophers.slack.com. https://invite.slack.golangbridge.org/ https://invite.slack.golangbridge.org/