From be86df976f71c2cf23759de1a43cdf93c1d4e92b Mon Sep 17 00:00:00 2001 From: wind57 Date: Wed, 10 Apr 2024 18:49:53 +0300 Subject: [PATCH] typo --- .../the-discoveryclient-route-definition-locator.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/spring-cloud-gateway/the-discoveryclient-route-definition-locator.adoc b/docs/modules/ROOT/pages/spring-cloud-gateway/the-discoveryclient-route-definition-locator.adoc index ddbb9ea4..707d6b21 100644 --- a/docs/modules/ROOT/pages/spring-cloud-gateway/the-discoveryclient-route-definition-locator.adoc +++ b/docs/modules/ROOT/pages/spring-cloud-gateway/the-discoveryclient-route-definition-locator.adoc @@ -3,7 +3,7 @@ You can configure the gateway to create routes based on services registered with a `DiscoveryClient` compatible service registry. -By default, the routes created use the protocol `lb://service-name` (where `service-name` is the String that `DsicoveryClient::getServices` will return) and this means that they are load-balanced. For that reason, you also need to include the `org.springframework.cloud:spring-cloud-starter-loadbalancer` dependency, so that it is available on the classpath. +By default, the routes created use the protocol `lb://service-name` (where `service-name` is the String that `DiscoveryClient::getServices` will return) and this means that they are load-balanced. For that reason, you also need to include the `org.springframework.cloud:spring-cloud-starter-loadbalancer` dependency, so that it is available on the classpath. To enable this, set `spring.cloud.gateway.discovery.locator.enabled=true` and make sure a `DiscoveryClient` implementation (such as Netflix Eureka, Consul, Zookeeper or Kubernetes) is on the classpath and enabled.