Re: Envoy

Matt Klein <mklein@...>

Thanks all for having me! Here is the link to the Envoy v2 API project:

We are probably 1 month or so away from basic parity with the v1 JSON APIs.

Please let me know if any of you have any other questions.


On Tue, Aug 15, 2017 at 10:01 AM, Alexis Richardson <alexis@...> wrote:

I think the Istio team are evaluating their options.  It is early days - new project etc

On Tue, 15 Aug 2017, 09:55 Justin Garrison <justinleegarrison@...> wrote:
Speaking of Istio, do we know if there are any plans around istio being donated to the CNCF? How does that affect inclusion of envoy (I'm assuming it doesn't)? I think it's good to have complimentary projects in the CNCF but worry about customer confusion as the projects get closer to end users. IMO containerd/rkt don't matter much to end users because they are not (usually) implementing them directly, but linkerd/istio may cause more confusion.

I know linkerd can be integrated under istio but it's not the default just as rkt under Kubernetes is available but not default.

I'm all in favor of envoy as part of the CNCF. I just wanted to voice my concerns.

Justin Garrison

On Tue, Aug 15, 2017 at 8:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:
kicking off a thread in case TOC community have questions or comments on Envoy

I have copied matt

Envoy next steps:
- alexis & ken follow up re sponsoring formal proposal & DD  
   - talk to end users
   - talk to istio re prometheus/envoy; also: opentracing
   - identify TOC contributors to help with DD

cncf-toc mailing list

Matt Klein
Software Engineer

Join to automatically receive all group messages.