You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some Spring Cloud components use the `DiscoveryClient` in order to obtain information about the local service instance. For
125
125
this to work, you need to align the Kubernetes service name with the `spring.application.name` property.
126
126
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
+
127
131
== Kubernetes native service discovery
128
132
129
133
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.
794
798
795
799
The projects that require middleware generally include a
796
800
`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
0 commit comments