News for hackers. Stuff that matters.
Re:Skipper – An HTTP router and reverse proxy for service co... by org3432 on Sunday January 06, 2019 @02:06PM (#18839949)
We tried this out a year or so ago and found that it's performance wasn't suitable for our use cases, it would increase costs too much.
Re:Skipper – An HTTP router and reverse proxy for service co... by doh on Sunday January 06, 2019 @02:15PM (#18839997)
Care to share some details? What's your use case? How would it negatively impact it?
Re:Skipper – An HTTP router and reverse proxy for service co... by org3432 on Sunday January 06, 2019 @02:27PM (#18840045)
The main use case we tested with was for a data analytics pipeline to ingest telemetry events from video games, but would have been generally used across all our services, target was about 1m/RPS for our load test. The CoreOS ALB controller for K8s out performed it significantly (I don't have the exact stats now), albeit it's not as feature rich as Skipper.
Re:Skipper – An HTTP router and reverse proxy for service co... by sszuecs on Monday January 07, 2019 @03:11AM (#18843612)
Can you share more information with us in a gh issue https://github.com/zalando/skipper/issues? I am interested in getting details: payload size, resource configuration and access patterns in your test case.

Skipper serves well microservice workloads for Zalando and other companies, for example shopgun https://medium.com/@roffe/kubernetes-in-production-shopgun-2....

Re:Skipper – An HTTP router and reverse proxy for service co... by wikibob on Monday January 07, 2019 @11:54AM (#18846882)
Just to note, the CoreOS ALB controller [0] has very little in common with the design of Skipper.

The ALB controller configures Amazon Cloud "Application Load Balancers" and adds a Kubernetes service as the upstream. There's nothing in the data path.

[0] Now adopted by SIG-AWS as https://github.com/kubernetes-sigs/aws-alb-ingress-controlle...

Re:Skipper – An HTTP router and reverse proxy for service co... by doh on Sunday January 06, 2019 @02:32PM (#18840071)
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.

Re:Skipper – An HTTP router and reverse proxy for service co... by sszuecs on Monday January 07, 2019 @03:20AM (#18843647)
I 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/
Re:Skipper – An HTTP router and reverse proxy for service co... by rdli on Sunday January 06, 2019 @06:15PM (#18841368)
Did you check out Ambassador by any chance?
Re:Skipper – An HTTP router and reverse proxy for service co... by doh on Sunday January 06, 2019 @06:22PM (#18841406)
I did. Its not that far from Gloo. I would like something that doesn’t require crazy amount of tooling and does require containers