Skip to content

Commit d270327

Browse files
author
Ryan Baxter
committed
update readme
1 parent 98b9e3e commit d270327

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,10 @@ spring.cloud.kubernetes.discovery.enabled=false
124124
Some Spring Cloud components use the `DiscoveryClient` in order to obtain information about the local service instance. For
125125
this to work, you need to align the Kubernetes service name with the `spring.application.name` property.
126126

127+
Spring Cloud Kubernetes can also watch the Kubernetes service catalog for changes and update the
128+
`DiscoveryClient` implementation accordingly. In order to enable this functionality you need to add
129+
`@EnableScheduling` on a configuration class in your application.
130+
127131
== Kubernetes native service discovery
128132

129133
Kubernetes itself is capable of (server side) service discovery (see: https://kubernetes.io/docs/concepts/services-networking/service/#discovering-services).
@@ -794,7 +798,7 @@ credentials and you already have those.
794798

795799
The projects that require middleware generally include a
796800
`docker-compose.yml`, so consider using
797-
https://compose.docker.io/[Docker Compose] to run the middeware servers
801+
https://docs.docker.com/compose/[Docker Compose] to run the middeware servers
798802
in Docker containers. See the README in the
799803
https://github.com/spring-cloud-samples/scripts[scripts demo
800804
repository] for specific instructions about the common cases of mongo,

0 commit comments

Comments
 (0)