Dave Cheney

For 0.15 I've landed #1350 and I plan to leave this issue here for the moment. Sending invalid updates to Envoy is a problem -- we shouldn't do that, but...

At the moment I don't believe Envoy offers the option to encapsulate an upstream, Envoy's word for Envoy to Pod traffic, TCP session in a PROXYv2 header. This is a...

Hello, Without support for PROXYv2 in envoy we cannot implement this feature. I would prefer not to leave this issue open indefinitely as there are no active plans to work...

Thank you for the reference to the Envoy issue. I'll reopen this and target it for beta1, hopefully Envoy 1.11 will be out by then.

Moving to 0.15 as the envoy 1.11.0 upgrade is complete #1242 Marking as help wanted because nobody is scheduled to work on this at the moment.

It looks like this feature is in master, but not 1.11. I'm moving this issue to the unplanned milestone as it is blocked on #1351

Thank you for raising this issue. I think the best solution to this is FDS which we’re waiting on. Maybe it’ll come in envoy 1.12. With that said I understand...

/cc @jpeach @youngnick I don't have a position on this; we've gone back and forth on what constitutes invalid deliberately and accidentally a few times in the past. My ask...

removing the bug tag, this is working as intended -- although the intention is the point of debate.

Perhaps a solution is we change contour to always assume the service/port combination is valid. The linkage between RDS and CDS is by name alone so if it turns out...