sszuecs

3 ms·

1.
by sszuecs 2y ago
Hi! I am one of the maintainers of https://opensource.zalando.com/skipper http proxy library, which can support similar cases. We use this at Zalando https://www.zalando.com/ in Kubernetes and allow develop
2.
by sszuecs 6y ago
the original spreadsheet was updated
3.
by sszuecs 6y ago
I sent them an E-Mail with a link to a copy https://docs.google.com/spreadsheets/d/1z5u-UrIkihxq_6tDwiau... .
4.
by sszuecs 8y ago
Running >100 Kuberenetes clusters with a team is already quite complex. Teams already struggle with Kubernetes core concepts and we have to make sure the time spent does not grow, because of some nice to have features that are not busine
5.
by sszuecs 8y ago
We skipper maintainers don't want to really comment on that, because it is very likely that if you do your own benchmarks you show only the good parts and not the bad parts. From our benchmarks we can outperform nginx in the pure routi
6.
by 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/
7.
by sszuecs 8y ago
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. Skipp
8.
by sszuecs 10y ago
In the past we used icinga at Zalando and it scaled for us to 40k checks, after that we got huge latency problems. We use now zmon https://github.com/zalando/zmon/ which is really great, because it scales the chec