Date
1 - 11 of 11
Envoy
alexis richardson
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
Richard Li
+1. We've deployed Envoy into production ourselves, and we also have folks using our API Gateway (Ambassador) built on Envoy.
We're happy to help in any way. Not sure what "DD" stands for?
On Tue, Aug 15, 2017 at 11:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:
kicking off a thread in case TOC community have questions or comments on EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
Justin Garrison <justinleegarrison@...>
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.
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 EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
alexis richardson
DD is due diligence!
toggle quoted message
Show quoted text
On Tue, 15 Aug 2017, 09:50 Richard Li <richard@...> wrote:
+1. We've deployed Envoy into production ourselves, and we also have folks using our API Gateway (Ambassador) built on Envoy.We're happy to help in any way. Not sure what "DD" stands for?On Tue, Aug 15, 2017 at 11:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:kicking off a thread in case TOC community have questions or comments on EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
alexis richardson
Ack
toggle quoted message
Show quoted text
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.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 EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
Matt Klein <mklein@...>
Thanks all for having me! Here is the link to the Envoy v2 API project: https://github.com/lyft/envoy-api
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.
Thanks,
Matt
On Tue, Aug 15, 2017 at 10:01 AM, Alexis Richardson <alexis@...> wrote:
AckI think the Istio team are evaluating their options. It is early days - new project etcOn 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.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 EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
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 :)
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:
AckI think the Istio team are evaluating their options. It is early days - new project etcOn 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.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 EnvoyI have copied mattEnvoy 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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719
Doug Davis <dug@...>
As for Istio vs Envoy... Istio uses Envoy under the covers so having both (eventually) in CNCF would be a nice pairing/outcome.
thanks
-Doug
_______________________________________________________
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
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:
- Ack
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
justingarrison.com
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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
Quinton Hoole
I can assist with the Envoy technical due diligence.
Regards
Q
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
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.
thanks
-Doug
_______________________________________________________
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:Ack
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
justingarrison.com
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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
alexis richardson
Thanks Quinton - I think we're good for now with ChrisL from Tigera, and some help from Google/Istio peeps.
On Mon, Aug 21, 2017 at 3:54 PM, Quinton Hoole via cncf-toc <cncf-toc@...> wrote:
I can assist with the Envoy technical due diligence.
Regards
Q
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@....io> 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@linuxfoundation.org>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>, "cncf-toc-bounces@....io" <cncf-toc-bounces@.... io>, 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.
thanks
-Doug
_______________________________________________________
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:Ack
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
justingarrison.com
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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719_____________________________________________ __
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
The formal proposal is on GitHub now, so please put any public commentary there: https://github.com/cncf/toc/pull/43
If all goes well, I plan on asking the TOC to call a vote by early Sept at the latest.
Thanks.
On Mon, Aug 21, 2017 at 6:02 PM, Alexis Richardson <alexis@...> wrote:
Thanks Quinton - I think we're good for now with ChrisL from Tigera, and some help from Google/Istio peeps.On Mon, Aug 21, 2017 at 3:54 PM, Quinton Hoole via cncf-toc <cncf-toc@...> wrote:I can assist with the Envoy technical due diligence.
Regards
Q
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@...o> 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@...g>
Cc: Alexis Richardson via cncf-toc <cncf-toc@...>, "cncf-toc-bounces@...o" <cncf-toc-bounces@... o>, 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.
thanks
-Doug
_______________________________________________________
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:Ack
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
justingarrison.com
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@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719_____________________________________________ __
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
--
Chris Aniszczyk (@cra) | +1-512-961-6719