5 ms·

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.

doh 8y ago
Care to share some details? What's your use case? How would it negatively impact it?
- org3432 8y ago
  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.
  - 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 ago
      Did you check out Ambassador by any chance?
      - doh 8y ago
        I 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 ago
      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/ https://invite.slack.golangbridge.org/
  - sszuecs 8y ago
    Can you share more information with us in a gh issue https://github.com/zalando/skipper/issues 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-2c280f0c0923 https://medium.com/@roffe/kubernetes-in-production-shopgun-2....
  - wikibob 8y ago
    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-controller/ https://github.com/kubernetes-sigs/aws-alb-ingress-controlle...

doh 8y ago

Care to share some details? What's your use case? How would it negatively impact it?

org3432 8y ago
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.
- 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 ago
    Did you check out Ambassador by any chance?
    - doh 8y ago
      I 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 ago
    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/ https://invite.slack.golangbridge.org/
- sszuecs 8y ago
  Can you share more information with us in a gh issue https://github.com/zalando/skipper/issues 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-2c280f0c0923 https://medium.com/@roffe/kubernetes-in-production-shopgun-2....
- wikibob 8y ago
  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-controller/ https://github.com/kubernetes-sigs/aws-alb-ingress-controlle...