Skip to content
This version of the documentation is currently under development. Select the stable version from the version drop down.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Load balancing

Page as Markdown
Configure load balancing in ambient mesh, from ztunnel’s automatic L4 round-robin to advanced L7 policies via waypoint proxies.
Ambient mesh distributes traffic across healthy endpoints automatically using round-robin load balancing at the ztunnel layer by default. You can configure more advanced behavior through Kubernetes service settings, Istio annotations, and DestinationRules.
Load balancing works together with outlier detection and failover to keep traffic flowing to healthy endpoints.
  • Load balancing: How traffic is distributed across healthy endpoints, such as through traffic distribution modes.
  • Outlier detection: How unhealthy endpoints are identified, such as through error thresholds and ejection time.
  • Failover: What happens when endpoints become unhealthy, such as routing to a different locality or following a priority order.
For detailed configuration options and component-specific behavior (ztunnel, waypoint, ingress gateway), see the Load balancing and failover section in Resiliency.
   Ztunnel (L4)
 Set up and test basic L4 load balancing and failover with ztunnel in an ambient mesh.
     Waypoints (L7)
 Set up L7 load balancing and failover with waypoint proxies, including custom DestinationRules for HTTP-aware behavior.
     L7 load balancing with kgateway
 Configure load balancing and failover for traffic entering the ambient mesh through Solo Enterprise for kgateway.
  
Traffic splittingMirroring