From 6971a7265c30421cc143209b24ed1a495427aa99 Mon Sep 17 00:00:00 2001 From: Johnny Burns Date: Fri, 19 Aug 2016 07:02:19 -0700 Subject: [PATCH] Health Check Link --- docs/intro/arch_overview/service_discovery.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/intro/arch_overview/service_discovery.rst b/docs/intro/arch_overview/service_discovery.rst index 8d20fe55cfe0..668ddfddcf5d 100644 --- a/docs/intro/arch_overview/service_discovery.rst +++ b/docs/intro/arch_overview/service_discovery.rst @@ -79,8 +79,9 @@ of pain. Envoy was designed from the beginning with the idea that service discovery does not require full consistency. Instead, Envoy assumes that hosts come and go from the mesh in an eventually consistent way. Our recommended way of deploying a service to service Envoy mesh configuration uses eventually -consistent service discovery along with active health checking (Envoy explicitly health checking -upstream cluster members) to determine cluster health. This paradigm has a number of benefits: +consistent service discovery along with :ref:`active health checking ` +(Envoy explicitly health checking upstream cluster members) to determine cluster health. This +paradigm has a number of benefits: * All health decisions are fully distributed. Thus, network partitions are gracefully handled (whether the application gracefully handles the partition is a different story).