Re: Envoy

Quinton Hoole

I can assist with the Envoy technical due diligence.



Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # E2-9

Email: quinton.hoole@...   ID#Q00403160

From: <cncf-toc-bounces@...> on behalf of Doug Davis via cncf-toc <cncf-toc@...>
Reply-To: Doug Davis <dug@...>
Date: Thursday, August 17, 2017 at 15:26
To: Chris Aniszczyk <caniszczyk@...>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>, "cncf-toc-bounces@..." <cncf-toc-bounces@...>, Varun Talwar <varuntalwar@...>
Subject: Re: [cncf-toc] Envoy

As for Istio vs Envoy... Istio uses Envoy under the covers so having both (eventually) in CNCF would be a nice pairing/outcome.

STSM | IBM Open Source, Cloud Architecture & Technology
(919) 254-6905 | IBM 444-6905 | dug@...
The more I'm around some people, the more I like my dog

Chris Aniszczyk via cncf-toc ---08/15/2017 06:30:16 PM---Just to expand on this, we've already spoken with the Istio team about a foundation home and the dis

From: Chris Aniszczyk via cncf-toc <cncf-toc@...>
To: Alexis Richardson <alexis@...>
Cc: Varun Talwar <varuntalwar@...>, Alexis Richardson via cncf-toc <cncf-toc@...>
Date: 08/15/2017 06:30 PM
Subject: Re: [cncf-toc] Envoy
Sent by: cncf-toc-bounces@...

Just to expand on this, we've already spoken with the Istio team about a foundation home and the discussions went well, it's still too early for them but we've planned to revisit the discussion later this year as the Istio community grows.

We love what they are doing and of course CNCF would be a great home for them IMHO :)

On Tue, Aug 15, 2017 at 12:01 PM, Alexis Richardson via cncf-toc <cncf-toc@...> 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

    cncf-toc mailing list

Chris Aniszczyk (@cra) | +1-512-961-6719_______________________________________________
cncf-toc mailing list

Join to automatically receive all group messages.