mattklein123

3 ms·

1. 1.▲
   Envoy joins the CNCF(medium.com)

   13 points by mattklein123 9y ago|0 comments
2. 2.▲
   Envoy: 7 months later(eng.lyft.com)

   176 points by mattklein123 9y ago|46 comments
3. 3.▲
   by mattklein123 10y ago

   Mainly just years of experience at different companies watching ZK, etcd, etc. fall over at scale and require teams of people to maintain them. We have had zero outages caused by our eventually consistent discovery system with active health
4. 4.▲
   by mattklein123 10y ago

   Visualization is going to be a big area of future investment for us. We already have some pretty cool tools internally and obviously lots of dashboards, etc. but we would love to have a dedicated UI for Envoy. If you know any good UI devs w
5. 5.▲
   by mattklein123 10y ago

   Currently we support SNI for client connections, not for server connections. There is no reason for this, just that we have not needed server-side SNI ourselves yet. Adding server SNI support would be a small change. Please file a GitHub is
6. 6.▲
   by mattklein123 10y ago

   Hi, I work at Lyft. To answer your questions: 1) There is added cost, though it varies depending on how many things Envoy is configured to do (e.g., logging, tracing, stats, rate limiting, health checking, etc.). Even in complex scenarios (
7. 7.▲
   by mattklein123 10y ago

   We will fix the docs, apologies. FYI, your README still says that "HTTP/2 support is in progress".