3 ms·
When Kuma is being deployed in multi-zone mode and a service from one zone wants to consume a service from another zone, does that mean that the outbound reques
by kh_hk 6y ago
When Kuma is being deployed in multi-zone mode and a service from one zone wants to consume a service from another zone, does that mean that the outbound request will automatically be routed to the correct address of the service (potentially in a different zone) while still honoring any custom "TrafficRoute" policies that the mesh administrators may have created in the meanwhile?
- fosk 6y agoYes. In Kuma the “.mesh” DNS zone will route to either an IP address of a replica of the service in the same zone, or to the IP address of a Kuma ingress in another zone for automatic cross-zone connectivity (only if mTLS is enabled so we can leverage SNI). Any TrafficRoute will be honored, and we can also apply zone-shifting rules by using the “kuma.io/zone“ tag in a “TrafficRoute” [1] policy. [1] - https://kuma.io/policies https://kuma.io/policies
- mikejulietbravo 6y agoIf I understand correctly, yes, this shouldn't be a problem for it to resolve. Check out here for more info > https://kuma.io/docs/0.7.1/documentation/deployments/#multi-zone-mode https://kuma.io/docs/0.7.1/documentation/deployments/#multi-...