From b3de20b21593990cd3da4ef517e3ca639b3ece51 Mon Sep 17 00:00:00 2001 From: Ryan Baxter Date: Thu, 20 Dec 2018 10:52:06 -0500 Subject: [PATCH] Fixing documentation --- docs/src/main/asciidoc/discovery-kubernetes-native.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/discovery-kubernetes-native.adoc b/docs/src/main/asciidoc/discovery-kubernetes-native.adoc index 5cb34e55..4485a680 100644 --- a/docs/src/main/asciidoc/discovery-kubernetes-native.adoc +++ b/docs/src/main/asciidoc/discovery-kubernetes-native.adoc @@ -3,7 +3,7 @@ Kubernetes itself is capable of (server side) service discovery (see: https://kubernetes.io/docs/concepts/services-networking/service/#discovering-services). Using native kubernetes service discovery ensures compatibility with additional tooling, like: istio https://istio.io (service mesh, capable of load balancing, ribbon, circuit breaker, failover and much more). -The caller service just needs to refer to names resolvable in particular kubernetes cluster then. Simplest implementation might use the spring `RestTemplate` referring to fully qualified domain name (FQDN) `http://..svc..local:`. +The caller service just needs to refer to names resolvable in particular kubernetes cluster then. Simplest implementation might use the spring `RestTemplate` referring to fully qualified domain name (FQDN) `http://{service-name}.{namespace}.svc.{cluster}.local:{service-port}`. Additionally, hystrix can be used for: