r high scale workloads.
--
*Srinivas Kotaru*
*From: *Clayton Coleman
*Date: *Wednesday, January 24, 2018 at 10:32 AM
*To: *Srinivas Naga Kotaru
*Cc: *users
*Subject: *Re: Heptio Contour
At this point in time, contour is still pretty new, so expect some rough
edges. I did a prototype of
3.9 will have haproxy 1.8, but the current level of http2 doesn’t
really help applications that aren’t willing to do passthrough. That
said, passthrough http2 should work.
> On Jan 24, 2018, at 2:54 PM, Tobias Brunner wrote:
>
>> On 24.01.2018 19:31, Clayton Coleman wrote:
>> In general, when co
On 24.01.2018 19:31, Clayton Coleman wrote:
> In general, when comparing to haproxy and the general state, here's the list
>
> PROs (envoy):
>
> * supports http2 natively
I would say this is a non-issue:
https://www.mail-archive.com/haproxy@formilux.org/msg28004.html
---
HTTP/2 (Willy Tarreau)
workloads.
--
Srinivas Kotaru
From: Clayton Coleman
Date: Wednesday, January 24, 2018 at 10:32 AM
To: Srinivas Naga Kotaru
Cc: users
Subject: Re: Heptio Contour
At this point in time, contour is still pretty new, so expect some rough edges.
I did a prototype of routes with envoy (similar to contour
At this point in time, contour is still pretty new, so expect some rough
edges. I did a prototype of routes with envoy (similar to contour, but
preserving the router features) a few months back, and identified a set of
challenges which made it not a great fit as a replacement for the OOTB
openshif
Hi.
-- Originalnachricht --
Von: "Srinivas Naga Kotaru (skotaru)"
An: "users"
Gesendet: 19.01.2018 19:36:18
Betreff: Heptio Contour
How it is different than Openshift router and what extra benefits it
brings? Anyone educate me to understand differences or possible
How it is different than Openshift router and what extra benefits it brings?
Anyone educate me to understand differences or possible use cases where it fit
into eco system? Or replacing ingress controller or will it solve ingress
controller 244 address limitations?
https://blog.heptio.com/annou
