Dave Cheney

Nothing more is planned for this issue before 1.0. Moving to the backlog

I think I understand the underlying problem here. To solve it we will have to do some large changes to the way we generate clusters from k8s endpoint sets. This...

@stevesloka I'm going to take this one. I'm worried we might need to move `route.services.strategy` up one level if we want to move from WeightedClusters to a Cluster with multiple...

I'm moving this issue to the backlog. Changing the way Contour generates clusters is too large a risk this close to the 1.0 release.

@michmike feels strongly that users test and qualify each release before deploying it so the notion of automatically upgrading seems antithetical. However, if folks want to do this they can...

I think there are two issues at play here, one is our support policy which states that when we make a new release, any other release is now unsupported. There...

> @SDBrett envoy makes the version available in each DiscoveryRequest in the Node message. hotdamn! when was that added?

@sudeeptoroy thank you for raising this issue. I believe that this should be possible to fix without having to add knowledge of the port envoy is listening on. Before we...

@sudeeptoroy I think the solution is to see if there is a way to prevent envoy adding any port to the redirect; ie http://foo.com -> https://foo.com shouldn't need a port.

Thank you for explaining. I played around with the rewriting options in envoy and it looks inescapable that we'll have to record the host port that traffic is nat'd into...