154eafe140
* 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 |
||
|---|---|---|
| .. | ||
| manager.go | ||
| manager_test.go | ||
| proxycfg.go | ||
| snapshot.go | ||
| state.go | ||
| state_test.go | ||
| testing.go | ||