graduation: envoy proposal #167
Conversation
Signed-off-by: Matt Klein <mklein@lyft.com>
|
RFC @cncf/toc |
|
RFC @cncf/toc proposal LGTM, devstats link is here: https://envoy.devstats.cncf.io |
|
|
||
| ### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope. | ||
|
|
||
| * Known end users include: AirBnb, Alibaba, Apple, Booking.com, Cookpad, DigitalOcean, eBay, Google, GO-JEK, |
There was a problem hiding this comment.
Please clarify whether all of these companies use Envoy in production. Also, please provide some more detail on the production usage for at least three of the most major uses, e.g. exactly what product/service uses Envoy, indication of scale of usage (both in terms of infrastructure size and number of users), how long it has been used in production etc. This will make it easier to judge the "quality and scope" aspect of the requirement.
There was a problem hiding this comment.
Many/most major users of Envoy are not forthcoming about exactly how they use it and at what scale. Although I know that almost all of the names listed here are in production, some at very large scale, I don't have permission to speak on their behalf. The only one I can speak officially on is Lyft.
@caniszczyk thoughts on best way to proceed here?
There was a problem hiding this comment.
@mattklein123 as a start, I would ask some adopters to see if they are comfortable publicly stating their usage of Envoy on this PR in more detail
There was a problem hiding this comment.
Speaking for the Lyft side of things:
- We run > 20K Envoy instances at once.
- 100% of edge and StS traffic flows through Envoy.
- The great majority of external partner traffic flows through Envoy.
- All MongoDB, Dynamo, and Redis traffic flows through Envoy.
- Total mesh traffic is 10M+ HTTP/gRPC RPS. Redis query RPS is many multiples of that.
@caniszczyk is going to help with the legwork to see what different companies are willing to say publicly.
There was a problem hiding this comment.
I'm not sure Cookpad case is major one though, we can share our usage of Envoy:
- Our recipe sharing service and some of other services are using Envoy. The Japanese recipe sharing service has more than 55 millions of average monthly users.
- 700~1200 Envoy instances are running in production.
- We use Envoy in production since November 2017.
- Most (more than 3/4) of our internal (service-to-service) traffics flow through Envoy.
There was a problem hiding this comment.
thanks all, @quinton-hoole-2 would you be comfortable kicking off a graduation vote then?
There was a problem hiding this comment.
I'm in favor of kicking off a vote.
There was a problem hiding this comment.
@caniszczyk Yes, I'm in favor of kicking off the graduation vote. Apologies for my delay replying.
There was a problem hiding this comment.
Thanks @quinton-hoole-2, I kicked off the graduation vote: https://lists.cncf.io/g/cncf-toc/message/2633
There was a problem hiding this comment.
@quinton-hoole-2 I remembered Huawei also has effort on Envoy, right?
|
At eBay, we are already using Envoy and will increase adoption significantly higher for the next year as well. |
caniszczyk
moved this from In progress (due diligence)
to TOC Approved (sponsors/voting)
in TOC Project Backlog
|
Envoy has graduated :) +1 binding TOC votes (9/9): Thanks @cncf/toc and all! |
caniszczyk
moved this from TOC Approved (sponsors/voting)
to Done
in TOC Project Backlog
At the request of @caniszczyk here is Envoy's application to become a graduated project.
Thank you for your consideration!
Signed-off-by: Matt Klein mklein@lyft.com