-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
If a service is imported from multiple meshes with the same name (e.g. using importAsLocal flag), we need to make sure that we're routing to all the meshes. If a single egress gateway is used for multiple federations, then the gateway should route out to all of the other meshes. This should work, but we may need to tweak locality settings to ensure things are working correctly. There may also be some work required to ensure locality is being applied correctly.
This task involves verifying whether or not using a single egress gateway to access multiple remote meshes will work when aggregating endpoints from the remote meshes into the local mesh. Verification should include:
- One endpoint exists for each mesh exporting the service
- Requests are distributed across each remote mesh
Additional Jira should be created if any follow up work is required (e.g. to make this work or prevent the use of a common egress gateway).
- is related to
-
OSSM-2473 federation: exported service names can clash when importing from >1 mesh
- Closed
-
OSSM-2474 federation: updating an ExportedServiceSet does not always work
- Closed
-
OSSM-2475 federation: Allow a single ingress/egress gateway to be used for multiple ServiceMeshPeers
- Closed
-
OSSM-2844 Release Notes for Service Mesh 2.1
- Closed