consul/agent/proxycfg
Matt Keeler 4c9577678e
xDS Mesh Gateway Resolver Subset Fixes (#7294)
* xDS Mesh Gateway Resolver Subset Fixes

The first fix was that clusters were being generated for every service resolver subset regardless of there being any service instances of the associated service in that dc. The previous logic didn’t care at all but now it will omit generating those clusters unless we also have service instances that should be proxied.

The second fix was to respect the DefaultSubset of a service resolver so that mesh-gateways would configure the endpoints of the unnamed subset cluster to only those endpoints matched by the default subsets filters.

* Refactor the gateway endpoint generation to be a little easier to read
2020-02-19 11:57:55 -05:00
..
manager.go Allow users to configure either unstructured or JSON logging (#7130) 2020-01-28 17:50:41 -06:00
manager_test.go OSS Changes for various config entry namespacing bugs (#7226) 2020-02-06 10:52:25 -05:00
proxycfg.go
snapshot.go xDS Mesh Gateway Resolver Subset Fixes (#7294) 2020-02-19 11:57:55 -05:00
state.go agent/proxycfg: fix dropped error in state.initWatchesMeshGateway() (#7267) 2020-02-18 14:41:01 +01:00
state_test.go OSS Changes for various config entry namespacing bugs (#7226) 2020-02-06 10:52:25 -05:00
testing.go Testing updates to support namespaced testing of the agent/xds… (#7185) 2020-02-03 09:26:47 -05:00