Merge pull request #58930 from rh-tokeefe/OSSM-3750

OSSM-3750: Incorrect default load balancing policy

Author: rolfedh

modules/ossm-routing-destination-rules.adoc

@@ -9,7 +9,7 @@
 
 Destination rules are applied after virtual service routing rules are evaluated, so they apply to the traffic's real destination. Virtual services route traffic to a destination. Destination rules configure what happens to traffic at that destination.
 
-By default, {SMProductName} uses a round-robin load balancing policy, where each service instance in the pool gets a request in turn. {SMProductName} also supports the following models, which you can specify in destination rules for requests to a particular service or service subset.
+By default, {SMProductName} uses a least requests load balancing policy, where the service instance in the pool with the least number of active connections receives the request. {SMProductName} also supports the following models, which you can specify in destination rules for requests to a particular service or service subset.
 
 * Random: Requests are forwarded at random to instances in the pool.
 * Weighted: Requests are forwarded to instances in the pool according to a specific percentage.

modules/ossm-routing-virtual-service.adoc

@@ -18,7 +18,7 @@ You can route requests dynamically to multiple versions of a microservice throug
 
 Requests are routed to services within a service mesh with virtual services. Each virtual service consists of a set of routing rules that are evaluated in order. {SMProductName} matches each given request to the virtual service to a specific real destination within the mesh.
 
-Without virtual services, {SMProductName} distributes traffic using round-robin load balancing between all service instances. With a virtual service, you can specify traffic behavior for one or more hostnames. Routing rules in the virtual service tell {SMProductName} how to send the traffic for the virtual service to appropriate destinations. Route destinations can be versions of the same service or entirely different services.
+Without virtual services, {SMProductName} distributes traffic using least requests load balancing between all service instances. With a virtual service, you can specify traffic behavior for one or more hostnames. Routing rules in the virtual service tell {SMProductName} how to send the traffic for the virtual service to appropriate destinations. Route destinations can be versions of the same service or entirely different services.
 
 .Procedure