Provide a way to configure Zone aware routing using Envoy Proxy

[vilva42]

Feature Description

Envoy allows you to configure zone aware routing for which you need to set cluster_type as EDS and locality information. It would be nice if there's a way to configure it through bootstrap options or provide guidance on how to accomplish this through Connect's L7 configs.

Use Case(s)

We would like to limit cross-AZ traffic.

[vilva42]

Update:

Had a discussion with @blake and found that this can be accomplished by creating service subsets. For example, you can place all your service instances under a default subset, let's say us-east-1 and an AZ subset us-east-1b. You can then use the AZ info from instance metadata with service-router's http header or query parameter to route to the same AZ subset. If no instances are found in the same AZ, requests are routed to the default subset. This way you don't run into the M:N Zone aware routing issue that envoy currently has. The downside of this approach is that it doesn't support subzone routing and requires minor code/config changes.

[jsosulska]

#6417 is linked to this.

[dschaaff]

I'm interested in using service subsets to accomplish this today. @vilva42 were you able to get this working?

[vilva42]

@dschaaff I haven't. We decided to move on from service mesh as we were on ECS and the integration was complex.

[Shaiou]

Hello, any issues about this issue ?

[aryaKetan]

Any update on this. Not sure if this issue is resolved but the issue remains open.

[Lord-Y]

A must have, any news?

[david-yu]

This feature is available in Consul Enterprise 1.17 and HCP Consul, as described in https://developer.hashicorp.com/consul/docs/v1.17.x/connect/manage-traffic/route-to-local-upstreams. As this is the official, supported solution from HashiCorp, we consider this issue to be resolved. Thanks so much for your interest and feedback!