|
Re: linkerd
FWIW I kicked off a thread about service meshes on the Network-SIG mailing list to gauge how those folks feel about making improvements to the k8s config model to facilitate solutions like
FWIW I kicked off a thread about service meshes on the Network-SIG mailing list to gauge how those folks feel about making improvements to the k8s config model to facilitate solutions like
|
By
Louis Ryan <lryan@...>
·
#401
·
|
|
Re: linkerd
thanks Louis, that is helpful
<cncf-toc@...> wrote:
thanks Louis, that is helpful
<cncf-toc@...> wrote:
|
By
alexis richardson
·
#400
·
|
|
Re: linkerd
@Alexis,
For taxation overheads as a strawman
- a simple HTTP/1.1 roundtrip latency percentile distribution at 10^n (n = 2..5) qps with a 4k response payload
- CPU time measurement of the proxy under
@Alexis,
For taxation overheads as a strawman
- a simple HTTP/1.1 roundtrip latency percentile distribution at 10^n (n = 2..5) qps with a 4k response payload
- CPU time measurement of the proxy under
|
By
Louis Ryan <lryan@...>
·
#399
·
|
|
Re: linkerd
We have HTTP/2 in alpha. Gory details here: https://github.com/BuoyantIO/linkerd/issues/174
Performance: a heady topic. That post is still accurate. Note that it's focused on a sidecar / low-mem
We have HTTP/2 in alpha. Gory details here: https://github.com/BuoyantIO/linkerd/issues/174
Performance: a heady topic. That post is still accurate. Note that it's focused on a sidecar / low-mem
|
By
William Morgan
·
#398
·
|
|
Re: linkerd
"standardized assessment" meaning "assessment"? or do you have something in mind?
"standardized assessment" meaning "assessment"? or do you have something in mind?
|
By
alexis richardson
·
#397
·
|
|
Re: linkerd
I think it would be useful to have some standardized assessment of the CPU, latency & memory footprint tax that products in this space have.
A feature comparison matrix would be nice too.
I think it would be useful to have some standardized assessment of the CPU, latency & memory footprint tax that products in this space have.
A feature comparison matrix would be nice too.
|
By
Louis Ryan <lryan@...>
·
#396
·
|
|
Re: linkerd
Thanks for that additional information, William.
Are there plans for linkerd to support HTTP2?
Is the most recent performance and overhead data available that in
Thanks for that additional information, William.
Are there plans for linkerd to support HTTP2?
Is the most recent performance and overhead data available that in
|
By
Brian Grant
·
#395
·
|
|
Re: linkerd
Sidebar:
Quite a long list of related projects can be found in the 'traffic
management' column of the landscape
Sidebar:
Quite a long list of related projects can be found in the 'traffic
management' column of the landscape
|
By
alexis richardson
·
#394
·
|
|
Re: linkerd
(adding Oliver, linkerd's maintainer)
Hi Brian,
Good point about Amalgam8, I should have mentioned them. Also maybe Netflix's Prana?
In my mind Traefik, Vulcand, etc. are largely targeted at ingress /
(adding Oliver, linkerd's maintainer)
Hi Brian,
Good point about Amalgam8, I should have mentioned them. Also maybe Netflix's Prana?
In my mind Traefik, Vulcand, etc. are largely targeted at ingress /
|
By
William Morgan
·
#393
·
|
|
linkerd
Hi, William. You briefly mentioned other similar proxies, such as Envoy. What do you see as linkerd's differentiating features or advantages compared to the others (Envoy, Traefik, Amalgam8)?
Also,
Hi, William. You briefly mentioned other similar proxies, such as Envoy. What do you see as linkerd's differentiating features or advantages compared to the others (Envoy, Traefik, Amalgam8)?
Also,
|
By
Brian Grant
·
#392
·
|
|
TOC slides for tomorrow
https://docs.google.com/presentation/d/17UEN7nz-BVSkzrdWqM2-DDMxrPzheZotTLJgbzzMk1k/edit?ts=57ee8991#slide=id.gd5ae4e962_2_136
https://docs.google.com/presentation/d/17UEN7nz-BVSkzrdWqM2-DDMxrPzheZotTLJgbzzMk1k/edit?ts=57ee8991#slide=id.gd5ae4e962_2_136
|
By
alexis richardson
·
#391
·
|
|
RFC Reminder: CNCF Graduation Criteria
Just a reminder to the TOC and wider CNCF community about the graduation criteria:
https://docs.google.com/document/d/1l6e-hW7C3S6xJjGn47hUKKxeFBxiamAK7kn5efSryxY/edit#
It would be great if folks can
Just a reminder to the TOC and wider CNCF community about the graduation criteria:
https://docs.google.com/document/d/1l6e-hW7C3S6xJjGn47hUKKxeFBxiamAK7kn5efSryxY/edit#
It would be great if folks can
|
By
Chris Aniszczyk
·
#390
·
|
|
DRAFT TOC Agenda for this week
Hi all,
This week's topics. Please shout if you want to add something.
Linkerd Pres.
Openzipkin Pres.
Graduation criteria.
-
Last few OpenTracing votes
Start Ref Arch vote
alexis
Hi all,
This week's topics. Please shout if you want to add something.
Linkerd Pres.
Openzipkin Pres.
Graduation criteria.
-
Last few OpenTracing votes
Start Ref Arch vote
alexis
|
By
alexis richardson
·
#389
·
|
|
CNCF Architectures
Hi,
I've seen the CNCF End User Reference Architecture here:
https://docs.google.com/presentation/d/1uMw2wkK0ubmc3khxqIuxK_rLK_wN89tNCnK7gDmTGR8/edit#slide=id.p4
In that doc there are comments about
Hi,
I've seen the CNCF End User Reference Architecture here:
https://docs.google.com/presentation/d/1uMw2wkK0ubmc3khxqIuxK_rLK_wN89tNCnK7gDmTGR8/edit#slide=id.p4
In that doc there are comments about
|
By
Jeremy Eder
·
#388
·
|
|
Re: [VOTE] OpenTracing Project Proposal
+1
By
Jonathan Boulle <jonathan.boulle@...>
·
#387
·
|
|
Re: [VOTE] OpenTracing Project Proposal
we have 6 YES votes from TOC
we have 6 YES votes from TOC
|
By
alexis richardson
·
#386
·
|
|
Re: [VOTE] OpenTracing Project Proposal
Yes
Kenneth Owens
CTO Cloud Native Platforms
Cloud Platforms and Services Group
kenowens@...
Phone: +1 408 424 0872
Mobile: +1 314 591 5708
Cisco.com
Think before you print.
This
Yes
Kenneth Owens
CTO Cloud Native Platforms
Cloud Platforms and Services Group
kenowens@...
Phone: +1 408 424 0872
Mobile: +1 314 591 5708
Cisco.com
Think before you print.
This
|
By
Kenneth Owens (kenowens) <kenowens@...>
·
#385
·
|
|
Re: [VOTE] OpenTracing Project Proposal
Yes!
- Bryan
By
Bryan Cantrill <bryan@...>
·
#384
·
|
|
Re: [VOTE] OpenTracing Project Proposal
Yes
By
Camille Fournier
·
#383
·
|
|
Re: [VOTE] OpenTracing Project Proposal
Yes (binding)
--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
Mesosphere Inc.
Follow us on Twitter: @mesosphere
Yes (binding)
--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos
Mesosphere Inc.
Follow us on Twitter: @mesosphere
|
By
Benjamin Hindman
·
#382
·
|