Dave Cheney

Based on https://github.com/projectcontour/contour/pull/1797#pullrequestreview-306974148 there's a good change that this setting doesn't do what I thought it did. Moving to the backlog for more investigation.

@jpeach are you working on this as part of #1714 ?

@jpeach thanks for working on #1415. Do you think there is anything more to do on this ticket for rc.2? If not, would you mind closing it or moving to...

Thanks for clarifying. Do you think you will have the bandwidth to tackle this for rc.2?

Thanks for raising this issue. When you say headless, do you mean, _doesn't have a service object_? If so, why not add a service object?

Thanks for your reply. Just to check I'm understanding your request, you want the ability to direct ingress traffic directly to one pod?

What's the use case for this? Is it that you want to be able to route to a specific pod because you need something like sticky sessions or header based...

Contour does not use kube proxy, we configure Envoy to communicate directly to the addresses listed in the Endpoint document. On Tue, 23 Jul 2019 at 10:56, moderation wrote: >...

Daz, Let’s not mix the streams. Please open a new feature request and outline the problem that you have that you’d like to solve with contour. Thanks Dave > On...

There is one tomorrow at 15:30 pacific https://projectcontour.io/community/