You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add unit test cases for api gateway supporting consul peering
* add compiled xds config golden files after running api-gw golden testcases
* fix(proxyCfg): propogate meshGatewayConfig to upstreams of API gateway (#23369)
* fix(proxyCfg): propogate meshGatewayConfig to upstreams of API gateway
- Fixed handleRouteConfigUpdate to properly propagate meshGatewayConfig to API gateway upstreams, which is required during XDS endpoint and cluster config generation.
- Added TestStateChangedAPIGateway test cases in state_test.go to validate API gateway update handling.
- Added API gateway-specific logging prefix (similar to mesh gateway) to help in debugging.
* fix(xds): correct endpoint config generation for API gateway in peered setups (#23370)
* fix(xds): correct endpoint config generation for API gateway in peered setups
- Previously, API gateway XDS endpoint generation incorrectly relied on cfgSnap.ConnectProxy config (instead of cgfSnap.APIGateway), which caused wrong/no endpoint configuration for peered environments.
- Changes made:
- Updated makeUpstreamLoadAssignmentForPeerService to fetch localGatewayEndpoint based on cfgSnap kind instead of always using cfgSnap.ConnectProxy.
- Updated endpointsFromDiscoveryChain to derive meshGatewayMode based on cfgSnap kind instead of always using cfgSnap.ConnectProxy.
- Recompiled golden test file to reflect fix.
* removed comment
* fix(xds): correct cluster config generation for API gateway in peered setups (#23371)
* fix(xds): correct cluster config generation for API gateway in peered setups
- Updated makeUpstreamClustersForDiscoveryChain to generate cluster config based on upstream endpoint type. Before this fix, it always generated cluster configs without endpoints, which is incorrect when the upstream endpoint type is hostname and mesh-gateway mode is remote; in such cases, endpoints must also be included in the cluster config.
- Added recompiled golden test file to reflect the fix.
* fix lint error
returnstructs.MeshGatewayModeDefault, fmt.Errorf("unexpected service kind %q when determining mesh gateway mode for cluster %q", cfgSnap.Kind, clusterName)
0 commit comments