From 287d18155805e7e4453fcd6ef07588eaacad98f4 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Mon, 12 Jun 2023 21:28:59 -0400 Subject: [PATCH] backport of commit 9c4b1303129b601bf326a0c39f50150741d53e8d (#17685) Co-authored-by: trujillo-adam --- website/content/docs/k8s/l7-traffic/failover-tproxy.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx b/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx index 6c76b6bd87..81bdc5e867 100644 --- a/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx +++ b/website/content/docs/k8s/l7-traffic/failover-tproxy.mdx @@ -1,10 +1,10 @@ --- layout: docs -page_title: Configure failover service instances +page_title: Configure failover services on Kubernetes description: Learn how to define failover services in Consul on Kubernetes when proxies are in transparent proxy mode. Consul can send traffic to backup service instances if a destination service becomes unhealthy or unresponsive. --- -# Configure failover service instances +# Configure failover services on Kubernetes This topic describes how to configure failover service instances in Consul on Kubernetes when proxies are in transparent proxy mode. If a service becomes unhealthy or unresponsive, Consul can use the service resolver configuration entry to send inbound requests to backup services. Service resolvers are part of the service mesh proxy upstream discovery chain. Refer to [Service mesh traffic management](/consul/docs/connect/l7-traffic) for additional information.